Very unimpressive issue reporting.
"The issue identified it as a problem"... what?
--
Elevated 500 Errors in Some US Regions
Update - We are still investigating the root cause for this incident. us-east-2 region isn’t receiving any network traffic at this point. We are also seeing some API request errors in other US regions, but not as high as us-east-2. Feb 12, 2026 - 23:58 UTC
Update - We continue to see increased levels of 500 errors across US-West and US-East regions. Our engineering team is investigating the issue. Feb 12, 2026 - 22:57 UTC
Update - The issue identified it as a problem in US-West with some impact in US-East and the impact seems to be primarily on reads rather than writes. Feb 12, 2026 - 22:37 UTC
Investigating - We have identified increasing 500 errors in some US regions and are actively investigating the cause. Feb 12, 2026 - 21:32 UTC
us-east-2 has been down for over 2 hours now
And still down. In my case, no auth and no reads.
If this had happened prior to 4PM Eastern, I would have been screwed on my main early-stage project. I guess it's time to move up the timeline on real backend with failover.