Degraded performance of Jira Automation rules

What to do

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

  Anything that failed between 2026-07-20 16:03 UTC and 2026-07-20 17:23 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 3

1. investigatingJul 20, 2026, 4:03 PM UTC

   We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.

   provider

2. identifiedJul 20, 2026, 4:58 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are currently seeing signs of improvements, however, affected users may experience delays in Jira and Jira Service management Automation rule executions. We'll continue to share additional updates here as more information is available.

   provider

3. resolvedJul 20, 2026, 5:23 PM UTC

   On July 20, 2026, some Jira and Jira Service Management users 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.

   provider

Corrections

None so far.

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