Findings Report on the July 8th Telstra Outage [pdf]
A surge in 500 internal server errors on AWS S3 service affected all users. No official fix or workaround is provided.
since
Here's why. Incidents from Wednesday, September 2, 2026 (UTC), ranked byBreakage Velocity.What is Breakage Velocity?A live score of how fast an outage or regression is spreading. The more people hit it, and the faster, the higher it climbs; it cools off as things calm down.Open-ended scale: under 25 low · 25+ elevated · 100+ high · 300+ extreme.
6 outages, 2 still active today. Worst: Render (<1 min).
A surge in 500 internal server errors on AWS S3 service affected all users. No official fix or workaround is provided.
since
OpenAI's codex API experienced a capacity error, causing users to receive messages indicating the model is at capacity. This issue affected users who attempted to use the API.
since
New account creation errors have been elevated, affecting new user sign-ups. The issue has been resolved.
– UTC
Degraded builds and deploys are currently affecting users. A fix has been implemented and is being monitored.
– UTC
The background job queue for the FlyIO Machines API experienced failures, affecting operational components. The issue has been resolved.
– UTC
A delay in DBM monitor evaluation began at Sep 2, 2026, 12:10 AM UTC. The issue was identified and is currently being monitored.
– UTC