Outage in Oso
Intermittent HTTP 401 errors in us-east-1
Resolved MinorIncident Report
From 22:03 - 22:26 UTC, requests to tasks deployed on the corrupted container instance incorrectly failed with HTTP 401 status codes. The corrupted instance was terminated at 22:26 at which point service was restored. The container instance was corrupted due to a race condition triggered by how AWS ECS launches tasks on container instances. We have since made changes to safeguard against this race condition.
Trusted by 1,000+ teams
Never miss outages in third-party dependencies
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
over 1 year ago - at 01/15/2025 08:51PM
From 22:03 - 22:26 UTC, requests to tasks deployed on the corrupted container instance incorrectly failed with HTTP 401 status codes. The corrupted instance was terminated at 22:26 at which point service was restored. The container instance was corrupted due to a race condition triggered by how AWS ECS launches tasks on container instances. We have since made changes to safeguard against this race condition.
Latest Oso outages
Fallback snapshots are delayed - 22 days ago
Oso Sync Processing Temporarily Paused - 27 days ago
Degraded Fallback Snapshot Freshness - 27 days ago
Oso Sync Degraded - 2 months ago
Elevated errors processing writes in eu-west-1 - 6 months ago
Never miss outages in third-party dependencies
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
