Vendor reports: degradedResolved · vendor status “resolved”Official status API

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

Reported by Tinybird · Data & Analytics · source last read 5 min ago

Official source (opens in a new tab)
Vendor start
Aug 12, 2026, 10:38 UTC
Vendor's clock
Resolved
Aug 12, 2026, 11:34 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
56 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Tinybird reports degraded: "Reads and writes degraded on US East (AWS) public cluster".[E1, E2]
  • The vendor marked it resolved at 2026-08-12 11:34 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-08-12 11:34 UTC · summary s1, evidence 2eea26b13ad368bf

Evidence (7)
  1. E1Tinybird reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Reads and writes degraded on US East (AWS) public cluster". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-08-12 10:38 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-08-12 11:34 UTC. (vendor)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Tinybird is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Aug 12, 2026, 10:38 UTCVendor-reported startVendor time
  2. Aug 12, 2026, 11:34 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.