Vendor reports: major outageResolved · vendor status “resolved”Official status API

Disrupted JIRA and JSM availability

Reported by Jira Service Management · Customer Support · source last read 5 min ago

Official source (opens in a new tab)
Vendor start
Feb 6, 2026, 20:24 UTC
Vendor's clock
Resolved
Feb 7, 2026, 05:38 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
9 h 13 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Jira Service Management reports major outage: "Disrupted JIRA and JSM availability".[E1, E2]
  • The vendor marked it resolved at 2026-02-07 05:38 UTC.[E3, E7]

Affected products and regions

  • Components: Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow, Opsgenie Incident Flow, Opsgenie Alert Flow, Jira Service Management Email Requests, Authentication and User Management, Purchasing & Licensing, Signup, Automation for Jira, Assist.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-02-07 05:38 UTC · summary s1, evidence b907b69781180563

Evidence (7)
  1. E1Jira Service Management reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Disrupted JIRA and JSM availability". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-02-06 20:24 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow, Opsgenie Incident Flow, Opsgenie Alert Flow, Jira Service Management Email Requests, Authentication and User Management, Purchasing & Licensing, Signup, Automation for Jira, Assist. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-02-07 05:38 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Jira Service Management Web, Service Portal, Opsgenie Incident Flow, Opsgenie Alert Flow, Opsgenie Incident Flow, Opsgenie Alert Flow, Jira Service Management Email Requests, Authentication and User Management, Purchasing & Licensing, Signup, Automation for Jira, Assist

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Jira Service Management is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Feb 6, 2026, 20:24 UTCVendor-reported startVendor time
  2. Feb 7, 2026, 05:38 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.