Outage in Oso
Some API endpoints incorrectly returning HTTP 4xx error codes
Resolved MinorIncident Report
From 20:03 - 20:35 UTC, some API endpoints incorrectly returned HTTP 4xx error codes. This was caused by a bad code change that resulted in feature flags not being properly applied. The bad code change was rolled back at 20:30 UTC and full service was restored by 20:35 UTC.
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/16/2025 09:01PM
From 20:03 - 20:35 UTC, some API endpoints incorrectly returned HTTP 4xx error codes. This was caused by a bad code change that resulted in feature flags not being properly applied. The bad code change was rolled back at 20:30 UTC and full service was restored by 20:35 UTC.
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
Intermittent HTTP 401 errors in us-east-1 - 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
