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

Some users in us-east-1 region unable to access Jira and JSM.

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

Official source (opens in a new tab)
Vendor start
Feb 5, 2026, 14:13 UTC
Vendor's clock
Resolved
Feb 5, 2026, 21:38 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
7 h 25 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 partial outage: "Some users in us-east-1 region unable to access Jira and JSM.".[E1, E2]
  • The vendor marked it resolved at 2026-02-05 21:38 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]
  • 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

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-02-05 21:38 UTC · summary s1, evidence 97085443d4f867f7

Evidence (7)
  1. E1Jira Service Management reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Some users in us-east-1 region unable to access Jira and JSM.". (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-05 14:13 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east-1. (Statuswall) source (opens in a new tab)
  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-05 21:38 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

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

Read from region codes written in the incident title, so treat it as inferred.

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 5, 2026, 14:13 UTCVendor-reported startVendor time
  2. Feb 5, 2026, 21:38 UTCVendor-reported resolutionVendor time

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