Resolved after 1 hour 33 minutes, affecting API, on February 24, 2026.
We released a fix around 17:08 UTC and verified that Location Status reporting has returned to normal behavior.
Affected components
Update timeline
- 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.
- identified Feb 24, 2026, 04:16 PM UTC
We have identified a possible cause of the increased latency and are working on a fix.
- 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.
- 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.
Your product runs on more than Omnivore
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services