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…”
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.
What changed
Struck in red is what imgix removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Increased errors for new render requests
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-09-01 15:30 UTC
AddedResolved time#5
Before: not present
After: 2026-09-01 16:22 UTC
AddedAffected components#6
Before: not present
After: Rendering Infrastructure
AddedUpdateidentified#7
Before: not present
After: We've identified an increase in errors for new rendering requests due to an ongoing incident with an upstream provider.
AddedUpdateidentified#8
Before: not present
After: 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.
AddedUpdatemonitoring#9
Before: not present
After: Error rates have returned to normal levels.
We are continuing to monitor the situation while awaiting an update from Google Cloud.