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.
Need to monitor Oso outages?
- Monitor all your external dependencies in one place
- Get instant alerts when outages are detected
- Be the first to know if service is down
- Show real-time status on private or public status page
- Keep your team informed
Latest Updates ( sorted recent to last )
RESOLVED
about 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
Elevated errors processing writes in eu-west-1 - 3 months ago
Platform degradation in some upstream AWS services - 4 months ago
Platform degradation for some upstream AWS services - 4 months ago
Website unavailable - 9 months ago
Some API endpoints incorrectly returning HTTP 4xx error codes - about 1 year ago
The Status Page Aggregator with Early Outage Detection
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 · 5850 services available
Integrations with
