Omnivore incident

Increase in Degraded Locations

Minor Resolved View vendor source →
Started
Feb 24, 2026, 03:44 PM UTC
Resolved
Feb 24, 2026, 05:17 PM UTC
Duration
1h 33m
Detected by Pingoru
Feb 24, 2026, 03:44 PM UTC

Affected components

API

Update timeline

  1. investigating Feb 24, 2026, 03:44 PM UTC

    Around 9:02 UTC, we noticed a steady increase in the number of Locations entering a "degraded" state. This seems related to a small increase in average Agent Heartbeat response times to slightly above 2 seconds. This is causing some Locations to flap between "online" and "degraded". Customers may see a minor increase in API response times as a result. We are actively investigating the cause at this time.

  2. identified Feb 24, 2026, 04:16 PM UTC

    We have identified a possible cause of the increased latency and are working on a fix.

  3. identified Feb 24, 2026, 04:37 PM UTC

    At this time, we believe the impact for the duration of this incident was limited to incorrectly reporting the Location Status. We no longer believe that API calls experienced increased latency or error rates.

  4. resolved Feb 24, 2026, 05:17 PM UTC

    We released a fix around 17:08 UTC and verified that Location Status reporting has returned to normal behavior.

Looking to track Omnivore downtime and outages?

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

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

5 free monitors · No credit card required