Tinybird incident

Reads and writes degraded on US East (AWS) public cluster

Minor Resolved View vendor source →

Tinybird experienced a minor incident on August 12, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2026, 11:34 AM UTC
Resolved
Aug 12, 2026, 11:34 AM UTC
Duration
—
Detected by Pingoru
Aug 12, 2026, 11:34 AM UTC

Update timeline

  1. investigating Aug 12, 2026, 10:38 AM UTC

    Status: Investigating We're investigating an issue causing delays in data ingestion for some workspaces in the the US East (AWS) region

  2. investigating Aug 12, 2026, 10:56 AM UTC

    Status: Investigating We're investigating a service disruption in our US East (AWS) public cluster that began at 10:25 UTC and is affecting both reads and writes: API queries may fail or return errors, and incoming data is being queued. Our team is actively investigating and working to restore stability.

  3. resolved Aug 12, 2026, 11:34 AM UTC

    Status: Resolved We have successfully identified the root cause of the US East (AWS) public cluster disruption and fully restored both read and write operations; our team is currently processing the backlog of queued inserts accumulated during the incident.