Oso incident

Some API endpoints incorrectly returning HTTP 4xx error codes

Notice Resolved View vendor source →

Oso experienced a notice incident on January 16, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jan 16, 2025, 08:00 PM UTC
Resolved
Jan 16, 2025, 08:00 PM UTC
Duration
—
Detected by Pingoru
Jan 16, 2025, 08:00 PM UTC

Update timeline

  1. resolved Jan 16, 2025, 09:01 PM UTC

    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.