Oso incident

Partially delayed writes

Major Resolved View vendor source →

Oso experienced a major incident on February 7, 2024 affecting Authorization APIs, lasting 4h 6m. The incident has been resolved; the full update timeline is below.

Started
Feb 07, 2024, 10:14 PM UTC
Resolved
Feb 08, 2024, 02:21 AM UTC
Duration
4h 6m
Detected by Pingoru
Feb 07, 2024, 10:14 PM UTC

Affected components

Authorization APIs

Update timeline

  1. investigating Feb 07, 2024, 10:14 PM UTC

    We are currently investigating a degradation in our replication infrastructure resulting in delays to persist data. Customers may experience permission errors on newly created resources. We'll update with more information soon. Please reach out if you have any questions or concerns.

  2. monitoring Feb 07, 2024, 10:46 PM UTC

    We've rolled back a previous change and rotated out impacted hosts. Write latency looks to have returned to normal, and we're continuing to monitor

  3. resolved Feb 08, 2024, 02:21 AM UTC

    We haven't seen any regressions since the last update, and are fully rolled back. We will update with a full post-mortem once we have done an investigation