Oso incident

Oso Sync Degraded

Notice Resolved View vendor source →
Started
Mar 05, 2026, 05:18 PM UTC
Resolved
Mar 06, 2026, 02:22 PM UTC
Duration
21h 4m
Detected by Pingoru
Mar 05, 2026, 05:18 PM UTC

Update timeline

  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.

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