Is Opsgenie Down?

No — Opsgenie is up

Opsgenie's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 172 ms

Right now

The verdict is the worse of these two. How we decide

Opsgenie's status page

opsgenie.status.atlassian.com · read 4 minutes ago · checked every 3 minutes

Operational

Opsgenie's components, as its status page reports them
Component	Status
Public Website	Operational

44 locations All operational

Open their status page

FlareWarden checks

app.opsgenie.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 172 ms
Checked: 2 hours ago

By region

Amsterdam reachable, 94 ms
Dallas reachable, 169 ms
Newark reachable, 81 ms
Paris reachable, 120 ms
San Jose reachable, 153 ms
Stockholm reachable, 211 ms
Sydney reachable, 306 ms
Toronto reachable, 247 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	40 ms	9 ms	10 ms	94 ms
Dallas	51 ms	32 ms	32 ms	169 ms
Newark	37 ms	7 ms	8 ms	81 ms
Paris	42 ms	15 ms	16 ms	119 ms
San Jose	42 ms	22 ms	22 ms	153 ms
Stockholm	111 ms	25 ms	26 ms	210 ms
Sydney	263 ms	1 ms	2 ms	306 ms
Toronto	165 ms	17 ms	18 ms	246 ms

We check that app.opsgenie.com loads, not every feature behind it. Test it yourself

History

Incidents Opsgenie reported

Since Oct 22, 4 days · from opsgenie.status.atlassian.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Opsgenie website availability

Measured by FlareWarden · app.opsgenie.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 265ms

Last 30 days

70-day clean streak

Sep 26 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of app.opsgenie.com from multiple regions every 6 hours. Opsgenie's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 70 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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.

Test it yourself

Related services

Opsgenie outage FAQ

Alerts show in Opsgenie but nobody got paged. What broke?

Notification delivery, not alert ingestion. Opsgenie separates taking an alert in from sending it out, and reports them as different components per region, so a channel such as SMS or voice can fail while the alert list updates normally. Until it recovers, treat the alert list as the source of truth and have whoever is on call watch it directly.

Are my heartbeat alerts real during an Opsgenie incident?

Treat them with suspicion. A heartbeat fires when Opsgenie does not receive the expected check-in, so an incident affecting heartbeat monitoring or integration ingestion produces expiry alerts for systems that are perfectly healthy. Confirm against the service's own monitoring before acting, and expect a cluster of these to resolve themselves when the incident closes.

Does an Opsgenie outage affect Jira Service Management?

Sometimes, because they share Atlassian infrastructure and some notification plumbing. Atlassian has reported incidents where voice notification delivery degraded for both Opsgenie and Jira Service Management customers at once. They are separate products with separate status pages, so check both when on-call paging and service desk notifications fail together.

How do we stay covered while paging is down?

Fall back to something that does not depend on the failing channel. Open the alert list in a browser and keep a person watching it, agree a group chat as the paging channel for the duration, and share direct phone numbers for the current on-call. If your monitoring can also post to chat or email directly, enable that path so alerts arrive without passing through Opsgenie.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Opsgenie itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Opsgenie goes down

We check Opsgenie every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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

Free plan available No credit card required