Opsgenie and Jira Service Management outage, September 14, 2026

On Monday, September 14, 2026, Atlassian reported a shared incident on the Opsgenie and Jira Service Management status pages: Disrupted Opsgenie/JSM availability. The incident is resolved. Updates ran Investigating at 12:46 p.m. ET, Identified at 1:16 p.m. ET, Monitoring at 1:27 p.m. ET, and Resolved at 1:43 p.m. ET (17:43 UTC), about 57 minutes. Resolved impact: delayed alert notifications and an inability to view alerts in the UI. Both product pages now list All Systems Operational.

Times below are Eastern (UTC-4). Atlassian's main status page listed All Systems Operational during this event; the Opsgenie and Jira Service Management pages are the source of truth [1][2][3].

Timeline

Incident: Disrupted Opsgenie/JSM availability on Opsgenie [1] and Disrupted Opsgenie/JSM availability on Jira Service Management [2]. Status: Resolved, posted 1:43 p.m. ET (17:43 UTC). Impact: critical / Partial System Outage while open. As of ~2:18 p.m. ET, both pages show All Systems Operational [1][2].

• 12:46 p.m. ET (16:46 UTC) — Investigating. "We are actively investigating reports of a service disruption affecting Opsgenie and Jira Service Management." Opsgenie listed US and EU Web Application and Mobile Application as Major Outage. JSM listed Jira Service Management Web and Service Portal as Major Outage [1][2].
• 1:16 p.m. ET (17:16 UTC) — Identified. "We have identified the likely cause of the issue, and our teams are diligently working on a mitigation." Those components moved from Major Outage to Degraded Performance. Atlassian did not name the cause [1][2].
• 1:27 p.m. ET (17:27 UTC) — Monitoring. "The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability." Affected components returned to Operational [1][2].
• 1:43 p.m. ET (17:43 UTC) — Resolved. "On September 14, 2026, Opsgenie and Jira Service Management experienced a disruption, and impacted users saw delayed alerts notification and inability to view the alerts in the user interface. The issue has now been resolved, and the service is operating normally for all affected customers" [1][2].

Atlassian has not published a separate root-cause analysis.

Components

Major Outage during the incident:

• Opsgenie: US Web Application; US Mobile Application; EU Web Application; EU Mobile Application.
• Jira Service Management: Jira Service Management Web; Service Portal.

At Identified, those components were listed Degraded Performance. At Monitoring they were listed Operational. As of ~2:18 p.m. ET they remain Operational [1][2].

Listed Operational on Opsgenie throughout Investigating: Alert Flow; Incident Flow; Email, SMS, Voice, and Mobile Notification Delivery; Heartbeat Monitoring; REST APIs; Incoming Email Service; Incoming and Outgoing Integration Flow; Signup, Login & Authorization; Opsgenie Actions; and the remaining listed components, including Public Website.

Listed Operational on JSM throughout Investigating: Email Requests; Authentication and User Management; Automation for Jira; Assets; Assist; Purchasing & Licensing; Signup; Opsgenie Incident Flow; Opsgenie Alert Flow.

Jira Software listed All Systems Operational for this event [4]. The incident was posted on the Opsgenie and JSM pages, not as a Jira Software incident.

Impact

Resolved customer impact, per Atlassian: delayed alert notifications, and inability to view alerts in the UI. Major Outage components were Opsgenie US and EU web and mobile apps, plus JSM Web and Service Portal. JSM Email Requests, authentication, automation, Assets, and Assist stayed listed Operational. Atlassian did not post a workaround.

StatusStack monitors Opsgenie at statusstack.com/service/opsgenie (HTTP 200; monitoring since September 2020) and Jira Service Management at statusstack.com/service/atlassian-jira-service-management (HTTP 200; monitoring since September 2024). One dashboard for Opsgenie, Jira Service Management, and the rest of the stack is faster than tab-hopping vendor status pages during an incident. Monitor Opsgenie, monitor Jira Service Management, or start monitoring free.

References

[1] Atlassian. (2026, September 14). Disrupted Opsgenie/JSM availability. Retrieved ~2:18 p.m. ET from https://opsgenie.status.atlassian.com and https://stspg.io/l2wv8vpxnhvm

[2] Atlassian. (2026, September 14). Disrupted Opsgenie/JSM availability. Retrieved ~2:18 p.m. ET from https://jira-service-management.status.atlassian.com and https://stspg.io/l18v31t3cqnq

[3] Atlassian. (2026, September 14). Atlassian Status. Retrieved ~2:18 p.m. ET from https://status.atlassian.com/

[4] Atlassian. (2026, September 14). Jira Status. Retrieved ~2:18 p.m. ET from https://jira-software.status.atlassian.com/

[5] StatusStack. (2026, September 14). Is Opsgenie Down? Retrieved ~2:18 p.m. ET from https://statusstack.com/service/opsgenie

[6] StatusStack. (2026, September 14). Is Atlassian Jira Service Management Down? Retrieved ~2:18 p.m. ET from https://statusstack.com/service/atlassian-jira-service-management