Skip to main content
Jira

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

Major outage Lasted 7h 25m · started · Jira's page

Level
confirmed
Worst impact
Major outage
Components
Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Regions
us, us-east-1
Down Index
62of 100

What to do

  • Check whether you use Jira Viewing content, Create and edit, Authentication and User Management, Search and 7 more in us, us-east-1. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 7h 25m it lasted.

    Anything that failed between 2026-02-05 14:13 UTC and 2026-02-05 21:38 UTC may need a replay.
  • Subscribe to Jira's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=jira works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Jira 7

  1. investigating

    Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same. We will provide update on the progress in next 60 minutes or sooner.

    provider

  2. identified

    Some users in the us-east-1 region cannot access Jira and JSM. We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution. We will provide update on the progress in next 60 minutes or sooner.

    provider

  3. identified

    We have identified the cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

    provider

  4. identified

    Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region. We will continue to share additional updates here as more information is available.

    provider

  5. identified

    Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation. We will continue to share additional updates here as more information is available.

    provider

  6. 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.

    provider

  7. resolved

    On February 5, 2026, JIRA and JIRA Service Management experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-2b51957a88

Is Jira still down?

No, this incident was resolved 2026-02-05 21:38 UTC. For Jira's live state, see https://down.guide/jira.

How long did it last?

7h 25m, from 2026-02-05 14:13 UTC to 2026-02-05 21:38 UTC, by the times Jira posted.

What was affected?

Jira named Viewing content, Create and edit, Authentication and User Management, Search and 7 more in us, us-east-1.

What caused it?

Jira hasn't published a root cause. If it does, it shows here.

Where does this come from?

Jira's official status page, https://jira-software.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.