- Level
- confirmed
- Worst impact
- Degraded
- Components
- Incident Flow, Incident Flow, Alert Flow, Alert Flow, Email Notification Delivery, Email Notification Delivery, Public Website, SMS Notification Delivery, SMS Notification Delivery, Voice Notification Delivery, Voice Notification Delivery, Mobile Notification Delivery, Mobile Notification Delivery, Heartbeat Monitoring, Heartbeat Monitoring, Incident REST API, Incident REST API, Alert REST API, Alert REST API, Heartbeat REST API, Heartbeat REST API, Incoming Email Service, Incoming Email Service, Incoming Integration Flow, Incoming Integration Flow, Outgoing Integration Flow, Outgoing Integration Flow, Signup, Login & Authorization, Signup, Login & Authorization, Opsgenie Actions, Opsgenie Actions, Web Application, Web Application, Mobile Application, Mobile Application, Configuration REST APIs, Configuration REST APIs, Reporting & Analytics, Reporting & Analytics, Pricing & Billing, Pricing & Billing, Logs, Logs, Incoming Call Routing, Incoming Call Routing
- Regions
- in
What to do
Check whether you use Opsgenie Incident Flow, Incident Flow, Alert Flow, Alert Flow and 41 more in in. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3d 3h it lasted.
Anything that failed between 2026-07-21 09:48 UTC and 2026-07-24 13:07 UTC may need a replay.Subscribe to Opsgenie's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=opsgenie works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Opsgenie 3
- identified
We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
provider
- identified
A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team.
provider
- resolved
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-1bcfb25a55
Is Opsgenie still down?
No, this incident was resolved 2026-07-24 13:07 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.
How long did it last?
3d 3h, from 2026-07-21 09:48 UTC to 2026-07-24 13:07 UTC, by the times Opsgenie posted.
What was affected?
Opsgenie named Incident Flow, Incident Flow, Alert Flow, Alert Flow and 41 more in in.
What caused it?
Opsgenie hasn't published a root cause. If it does, it shows here.
Where does this come from?
Opsgenie's official status page, https://opsgenie.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.