Oso incident

Platform degradation for some upstream AWS services

Notice Resolved View vendor source →

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

Started
Oct 20, 2025, 10:14 AM UTC
Resolved
Oct 20, 2025, 07:00 AM UTC
Duration
—
Detected by Pingoru
Oct 20, 2025, 10:14 AM UTC

Update timeline

  1. resolved Oct 20, 2025, 10:14 AM UTC

    Between Oct 20 07:11 AM UTC and Oct 20 09:27 AM UTC, our system alarms for AWS started paging the On-Call team. We confirmed from the AWS status page that AWS was having an incident: https://health.aws.amazon.com/health/status AWS has reported that they have found the root cause and customers should be seeing recovery. Our internal monitoring dashboards have been available throughout this time and report that the Oso Cloud platform has been handling authorization decisions and write traffic without disruption. Given this, we currently believe there is no visible impact for Oso customers. We will continue to monitor and share any relevant status updates.