Skip to main content
Jira

Degraded performance of Jira and JSM automations in US East

Degraded Lasted 1h 19m · started · Jira's page

Level
confirmed
Worst impact
Degraded
Components
Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
Regions
us

What to do

  • Check whether you use Jira Viewing content, Create and edit, Authentication and User Management, Search and 7 more in us. 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 1h 19m it lasted.

    Anything that failed between 2026-06-02 15:32 UTC and 2026-06-02 16:51 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 2

  1. investigating

    We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.

    provider

  2. resolved

    On June 2, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.

    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-4f8ca439b3

Is Jira still down?

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

How long did it last?

1h 19m, from 2026-06-02 15:32 UTC to 2026-06-02 16:51 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.

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.