We started checking Opsgenie on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Opsgenie reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Opsgenie's own status page declared. Below it, any public chatter we saw about Opsgenie and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Opsgenie's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Opsgenie in the last 24 hours, which is not evidence that nothing is wrong.
Opsgenie's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Opsgenie's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Opsgenie next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
733
US-West
99.83%
581
Europe
99.81%
531
Asia-Pacific
100.00%
321
Their declared record
Opsgenie's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Disrupted Opsgenie/JSM availabilityMajor outage
Sep 14, 2026, 4:46 PM UTC to Sep 14, 2026, 5:43 PM UTC (57 min)postmortem published
their latest update (Sep 18, 2026, 5:02 PM UTC): ### Summary
On September 14, 2026, between 15:30 and 17:10 UTC, Atlassian customers using Opsgenie, Jira Service Management, and Compass experienced delays in receiving alert notifications and intermittent failures when using Ops features. The issue was triggered by long-running…
Issues with Microsoft Teams notifications for Opsgenie customersPartial outage
Aug 27, 2026, 10:26 AM UTC to Sep 3, 2026, 6:06 AM UTC (6d 19h)resolved
their latest update (Sep 3, 2026, 6:06 AM UTC): On August 19, we identified an issue affecting the delivery of Microsoft Teams notifications for Opsgenie standalone customers. The root cause was attributed to an operational error caused by our external partner, and they have taken corrective measures to restore services.
If …
Voice call failures for some India based numbersMinor incident
Jul 21, 2026, 9:48 AM UTC to Jul 24, 2026, 1:07 PM UTC (3d 3h)resolved
their latest update (Jul 24, 2026, 1:07 PM UTC): 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 expe…
Atlassian Cloud Services impactedPartial outage
Oct 20, 2025, 7:56 AM UTC to Oct 21, 2025, 5:24 AM UTC (21h 28m)postmortem published
their latest update (Oct 24, 2025, 5:54 PM UTC): ### Postmortem publish date: Nov 19th, 2025
### Summary
All dates and times below are in UTC unless stated otherwise.
Customers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service…
Delays in Opsgenie, JSM Ops and Compass Ops notificationsMinor incident
Sep 30, 2025, 2:07 PM UTC to Sep 30, 2025, 2:32 PM UTC (25 min)resolved
their latest update (Sep 30, 2025, 2:32 PM UTC): Between 13:10 UTC to 14:00 UTC, we experienced notification delay for Jira Service Management, Opsgenie, and Compass in only EU-region. The issue has been resolved and the service is operating normally.
Delays observed at JSM, Opsgenie and Compass alert search functionality in US RegionPartial outage
Sep 10, 2025, 3:23 PM UTC to Sep 11, 2025, 6:45 PM UTC (1d 3h)postmortem published
their latest update (Sep 24, 2025, 6:24 AM UTC): ### **SUMMARY**
Between September 10, 2025, at 13:56 UTC and September 11, 2025, at 14:40 UTC, Jira Service Management, Compass Cloud Operations, and Opsgenie customers in the U.S. region experienced degraded performance across web and mobile applications, as well as Alert REST …
Degraded performance in Opsgenie and JSM operationsAll systems operational
Jun 19, 2025, 3:21 PM UTC to Jun 19, 2025, 4:37 PM UTC (1h 16m)resolved
their latest update (Jun 19, 2025, 4:37 PM UTC): This incident has been resolved.
Degraded performance in Opsgenie and JSM operationsAll systems operational
Jun 17, 2025, 12:37 PM UTC to Jun 17, 2025, 12:47 PM UTC (10 min)resolved
their latest update (Jun 17, 2025, 12:47 PM UTC): This incident has been resolved, and Jira Service Management and Opsgenie are back in operational mode.
Delays observed at JSM and Opsgenie alert search functionalityMinor incident
May 10, 2025, 7:08 AM UTC to May 10, 2025, 10:51 AM UTC (3h 43m)resolved
their latest update (May 10, 2025, 10:51 AM UTC): All search functionality is operational without any latency. Thank you for your patience.
Schedule API are getting timed outAll systems operational
Apr 4, 2025, 10:05 AM UTC to Apr 4, 2025, 10:52 AM UTC (47 min)resolved
their latest update (Apr 4, 2025, 10:52 AM UTC): This incident has been resolved.
Showing the 10 most recent of 50 incidents Opsgenie has declared in the history we hold.
These entries are Opsgenie's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Opsgenie's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.