Jira: Degraded performance of Jira and JSM automations in US East
Affected components: Purchasing & LicensingMobileMarketplaceAutomation for JiraCreate and editSignupViewing contentAdministrationSearchAuthentication and User ManagementNotifications
Timeline of updates
- 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.
- 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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7fc9f262c98277d6…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Jira, started 2026-06-02 15:32 UTC, resolved after 1.3 h, 2 update(s).
- Title
- Degraded performance of Jira and JSM automations in US East
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/incidents/4drnxvxspl0g
Jira profileRecent Jira incidentsAll outages on June 2, 2026Jira in June 2026MarkdownJSON