Vendor reports: degradedResolved · vendor status “resolved”Official status API
US - Increased delays on alert flow
Reported by Opsgenie · Observability & Incident · source last read 3 min ago
- Vendor start
- Apr 30, 2024, 12:52 UTC
- Vendor's clock
- Resolved
- Apr 30, 2024, 16:13 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 3 h 21 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Components: Alert Flow, Heartbeat Monitoring, Alert REST API, Web Application, Mobile Application, Incoming Call Routing.[E6]
What is unknown
- Which regions are affected: the vendor did not say.[E5]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2024-04-30 16:13 UTC · summary s1, evidence 6dd41c974b0ad8e3
Evidence (7)
- E1Opsgenie reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "US - Increased delays on alert flow". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2024-04-30 12:52 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Alert Flow, Heartbeat Monitoring, Alert REST API, Web Application, Mobile Application, Incoming Call Routing. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2024-04-30 16:13 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Alert Flow, Heartbeat Monitoring, Alert REST API, Web Application, Mobile Application, Incoming Call Routing
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Opsgenie is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Apr 30, 2024, 12:52 UTCVendor-reported startVendor time
- Apr 30, 2024, 16:13 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.