Rewindex

CompaniesimgixIncidents

imgix: Increased errors for new render requests

MajorStatus: resolvedStarted Resolved (51 min)4 updatesstspg.io (opens in new tab)
Part of an outage event

Google Cloud us-central1 outage, Sep 1, 2026 · 47 vendors, 54 incidents

imgix’s incident blames Google Cloud as the cause. (hop 1, posted +49 min vs Google Cloud’s own post)

“…o normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud. This incident has been resolved. We have identified a correlation with an ongoing Google Cloud i…”

Swipe sideways to see the whole diagram.

blamed GitHubblamed TwilioGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed Google CloudPinecone, Elastic Cloud, FullStory +51 to 4 hours later6 vendors, 6 blamed Google CloudApollo GraphQL, Temporal Cloud, Clerk +3GitHubposted +18 min, did not name Google CloudBolt.new+24 minTwilioposted +1 h 42 min, did not name Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 minimgix (this incident)posted +49 min
blamed GitHubblamed TwilioGoogle Cloud us-central1posted 14:42 UTCWithin an hour8 vendors, 8 blamed GoogleCloudPinecone, Elastic Cloud,FullStory +51 to 4 hours later6 vendors, 6 blamed GoogleCloudApollo GraphQL, TemporalCloud, Clerk +3GitHubposted +18 min, did not nameGoogle CloudBolt.new+24 minTwilioposted +1 h 42 min, did notname Google CloudGorgias, Iterable+2 h 23 min to +2 h 37 minimgix (this incident)posted +49 min
imgix is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud us-central1<br/>posted 14:42 UTC"]:::root
  h1["Within an hour<br/>8 vendors, 8 blamed Google Cloud<br/>Pinecone, Elastic Cloud, FullStory +5"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>6 vendors, 6 blamed Google Cloud<br/>Apollo GraphQL, Temporal Cloud, Clerk +3"]:::blames
  root --> h4
  p0["GitHub<br/>posted +18 min, did not name Google Cloud"]:::timing
  root -.-> p0
  k0["Bolt.new<br/>+24 min"]:::hop2
  p0 -->|"blamed GitHub"| k0
  p1["Twilio<br/>posted +1 h 42 min, did not name Google Cloud"]:::timing
  root -.-> p1
  k1["Gorgias, Iterable<br/>+2 h 23 min to +2 h 37 min"]:::hop2
  p1 -->|"blamed Twilio"| k1
  me["imgix (this incident)<br/>posted +49 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Rendering Infrastructure

Timeline of updates

  1. identified

    We've identified an increase in errors for new rendering requests due to an ongoing incident with an upstream provider.

  2. identified

    We have identified a correlation with an ongoing Google Cloud incident, which reports elevated packet loss and errors for multiple services. We will continue to monitor error rates and provide further updates as Google Cloud shares more information.

  3. monitoring

    Error rates have returned to normal levels. We are continuing to monitor the situation while awaiting an update from Google Cloud.

  4. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

imgix profileRecent imgix incidentsMarkdownJSON