Is Opsgenie Down?
Reachable from all 8 checked regions
Average response time: 177ms
Last checked · checks run every 6 hours
Official status page: https://opsgenie.status.atlassian.com
Opsgenie uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 56 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
56-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Opsgenie does
Opsgenie is Atlassian's on-call tool: it takes alerts from monitoring systems, decides who is on call, and escalates by push, SMS, email and phone until somebody acknowledges. It sits in the path of every other outage you have, which makes its own failures particularly awkward, because the system meant to tell you something broke is the thing that broke.
What an outage looks like
Alerts arrive in the web application but no notifications go out, so nobody is paged. One delivery channel fails while others work, commonly SMS or voice in a single region. Integrations stop ingesting, so monitoring tools report sending alerts that never appear. Heartbeat monitors expire and fire false alarms about healthy systems. Escalation policies stall midway through a chain.
What to do about it
Opsgenie's status page reports each delivery channel separately for the US and EU regions: email, SMS, voice and mobile notifications, plus alert and incident flow, heartbeat monitoring and the REST APIs. Match the failing channel there. If notifications are the affected part, watch the alert list directly and tell the on-call rota to poll it rather than waiting to be paged.
Is it down for everyone, or just you?
If this page says Opsgenie is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Opsgenie outage FAQ
Alerts show in Opsgenie but nobody got paged. What broke?
Are my heartbeat alerts real during an Opsgenie incident?
Does an Opsgenie outage affect Jira Service Management?
How do we stay covered while paging is down?
How we measure this
- We request Opsgenie's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Opsgenie publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Opsgenie goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring