Oso Outage History

Oso is up right now

There were 4 Oso outages since March 5, 2026 totaling 244h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://oso.statuspage.io

Notice April 15, 2026

Fallback snapshots are delayed

Detected by Pingoru
Apr 15, 2026, 02:35 PM UTC
Resolved
Apr 23, 2026, 08:22 PM UTC
Duration
8d 5h
Timeline · 3 updates
  1. identified Apr 15, 2026, 02:35 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Apr 15, 2026, 03:15 PM UTC

    The issue has resolved. We are keeping in a Monitoring status while we work on a longer term fix to resolve the underlying root cause.

  3. resolved Apr 23, 2026, 08:22 PM UTC

    We have implemented a fix to mitigate future occurrence of this issue.

Read the full incident report →

Minor April 10, 2026

Oso Sync Processing Temporarily Paused

Detected by Pingoru
Apr 10, 2026, 05:05 AM UTC
Resolved
Apr 10, 2026, 08:37 PM UTC
Duration
15h 32m
Timeline · 2 updates
  1. identified Apr 10, 2026, 05:05 AM UTC

    We have temporarily paused Oso Sync processing while we resolve an infrastructure issue. Syncs submitted during this window will not be processed. Authorization requests via Oso Cloud are unaffected. We will provide updates as the situation progresses.

  2. resolved Apr 10, 2026, 08:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 10, 2026

Degraded Fallback Snapshot Freshness

Detected by Pingoru
Apr 10, 2026, 03:23 AM UTC
Resolved
Apr 10, 2026, 01:43 PM UTC
Duration
10h 20m
Timeline · 2 updates
  1. identified Apr 10, 2026, 03:23 AM UTC

    We are investigating an issue affecting fallback snapshot freshness. Our team has identified the cause and is actively working on remediation. We will provide updates as the situation progresses.

  2. resolved Apr 10, 2026, 01:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 5, 2026

Oso Sync Degraded

Detected by Pingoru
Mar 05, 2026, 05:18 PM UTC
Resolved
Mar 06, 2026, 02:22 PM UTC
Duration
21h 4m
Timeline · 3 updates
  1. identified Mar 05, 2026, 05:18 PM UTC

    We have identified an issue with our integration with S3 that is causing Oso Sync jobs to intermittently fail or time out. We have escalated the issue to AWS and are exploring other mitigations we can make.

  2. monitoring Mar 06, 2026, 04:24 AM UTC

    We've deployed a fix and are monitoring the results.

  3. resolved Mar 06, 2026, 02:22 PM UTC

    Since deploying the fix, we have not observed additional failures or timeouts related to our integration with S3.

Read the full incident report →

Looking to track Oso downtime and outages?

Pingoru polls Oso's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Oso reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Oso alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Oso for free

5 free monitors · No credit card required