Resolved after 1 hour 6 minutes, affecting Opsgenie, on March 12, 2026.
We've identified a drop in inbound traffic to incident.io "incident.io": http://incident.io from Opsgenie. This means that alerts may be slow to show up in incident.io "incident.io": http://incident.io, and paging via Opsgenie may be slow to reflect updates. This appears to be an issue with outbound webhooks on Opsgenie's side, we're monitoring the situation and will update as we know more.
Affected components
Update timeline
- identified Mar 12, 2026, 01:20 PM UTC
We've identified a drop in inbound traffic to incident.io "incident.io": http://incident.io from Opsgenie. This means that alerts may be slow to show up in incident.io "incident.io": http://incident.io, and paging via Opsgenie may be slow to reflect updates. This appears to be an issue with outbound webhooks on Opsgenie's side, we're monitoring the situation and will update as we know more.
- resolved Mar 12, 2026, 02:27 PM UTC
Traffic appears to be back to normal levels now.
Your product runs on more than incident.io
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