Jira change history

Major job-processing degradation affected Jira, Confluence, Bitbucket Cloud, Forge apps and Jira Service Management across all commercial cloud regions, delaying tasks and notifications and leaving SLA components missing; interactive use was unaffected. Logged from 2026-10-01 02:55 UTC to 2026-10-01 07:51 UTC (4 h 55 min), it was resolved after a fix.

JIRA’s critical US East disruption started at 2026-09-03 15:57 UTC and resolved at 2026-09-03 17:02 UTC (computed duration: 1 h 4 min), leaving affected users unable to access services. Recovery began at 16:15 UTC after mitigation; the postmortem attributes the disruption affecting Jira and Jira Service Management to a progressive rollout of a caching change.

Jira reported a major outage fetching mail from Microsoft accounts, disrupting email-based creation and updates of work items and potentially returning 500 errors. It started at 2026-08-31 18:28 UTC and was resolved at 2026-09-01 05:18 UTC, lasting 10 h 49 min; Atlassian reported full recovery across impacted services.

A critical outage made Jira Cloud, Jira Service Management and Confluence unavailable to affected users in Western Europe and Southeast APAC. The incident ran from 2026-08-27 04:22 UTC to 2026-08-27 05:16 UTC (53 min); Atlassian rolled out a fix, and its postmortem attributed the disruption to a defective proxy routing-layer code change.

Jira reported a major degradation delaying email, mobile and slack notifications for Jira, JSM and Confluence from 2026-08-25 08:42 UTC to 2026-08-25 14:33 UTC, lasting 5 h 51 min. Teams applied corrective measures in an impacted region; the vendor confirmed resolution and normal service for all customers.

Jira recorded a critical service-access incident affecting some Central European users, starting 2026-08-07 11:30 UTC and resolved 2026-08-07 12:52 UTC (1 h 21 min). The vendor separately reported user impact between 10:27 UTC and 11:49 UTC, applied a fix, and confirmed normal service for all customers.

Jira’s major Jira and Confluence incident ran from 2026-07-06 09:23 UTC to 2026-07-06 13:04 UTC (3 h 40 min). EU automation, user-search, user-picker and assets were affected; outage-period data processing requests were not completed. Fixes restored service; the postmortem cited core identity service database saturation and a broader 06:51–20:17 UTC disruption window.

Jira reported a major outage affecting Jira and JSM customers using Microsoft OAuth to create tickets from email: incoming email could not be read. It started at 2026-06-19 22:46 UTC and was resolved at 2026-06-26 05:13 UTC, lasting 6 days 6 h. New email processing was fixed; affected customers were instructed to re-authorize their Microsoft mail server.

Some Jira Service Management and Jira Cloud customers experienced intermittent errors and degraded performance viewing boards and work items in a major-impact incident. It started at 2026-06-09 05:29 UTC and was resolved at 2026-06-09 18:28 UTC, lasting 12 h 58 min. Jira reported applying a fix and restoring normal operations at 10:36 UTC.

Jira reported a major incident affecting loading, creating and viewing work items in some regions, starting 2026-06-06 23:21 UTC. A fix was implemented, and the incident was resolved at 2026-06-07 00:13 UTC; the reported duration was 51 min.

Jira Software, Jira Service Management, and Jira Work Management had major degradation in Europe, blocking issues, boards, and backlogs and causing transition, comment, and navigation errors. Recorded from 2026-06-01 07:40 UTC to 2026-06-01 13:23 UTC (5 h 42 min), the incident involved caching infrastructure autoscaling failure; Atlassian deployed a fix to prevent recurrence.

Jira reported a critical outage affecting access to multiple Atlassian Cloud products, including Jira Cloud and Confluence, starting 2026-05-14 06:41 UTC and lasting 6 min. Atlassian reported full recovery at 2026-05-14 06:48 UTC; its postmortem cited a deployment-orchestration race condition during a core identity service rollback in us-east.

Jira reported major automation delays for some Jira, Jira Service Management and JSM Assist users, starting 2026-05-13 01:37 UTC and lasting 8 h 21 min. Services were fully operational and all delayed automation events processed at 2026-05-13 09:59 UTC; the postmortem cited a latent bug in the event processing pipeline.

Jira users were unable to log time on business boards in a major incident affecting Create and edit. It started at 2026-05-06 03:18 UTC and lasted 3 h 21 min, ending at 2026-05-06 06:39 UTC. Jira deployed a fix and confirmed normal service for all affected customers.

A critical Jira outage caused work-item error pages and degraded editing across all Jira and Jira Service Management Cloud tenants; Jira boards and support-ticket access were also affected. Recorded from 2026-05-02 00:55 UTC to 2026-05-02 02:48 UTC (1 h 52 min), service was restored. The postmortem cited schema incompatibility.

A critical disruption affected Jira and Confluence automation rules invoking Rovo agents, causing some automations not to complete as expected. The incident started at 2026-04-14 12:12 UTC and was resolved at 2026-04-14 16:11 UTC, lasting 3 h 58 min; the vendor confirmed normal service but provided no specific cause or fix.

A critical incident caused search errors in Jira and Confluence, also affecting Customer Service Management, Asset Reports, Jira Service Management and Focus dashboards. Recorded from 2026-04-08 05:41 UTC to 2026-04-08 11:43 UTC (6 h 2 min), it was resolved for all affected customers; the postmortem reports a broader disruption window of 04:46 UTC–12:09 UTC.

Jira reported critical delays in event-triggered automations for some Cloud customers starting 2026-03-18 11:29 UTC, lasting 16 h 38 min until resolution at 2026-03-19 04:08 UTC. Scheduled, manual, and incoming-webhook triggers operated normally; historical-event replays remained underway for some high-volume customers at resolution. The postmortem attributed the incident to an internal configuration change.

Some APAC customers experienced delayed automations in Jira, Jira Service Management, Jira Work Management, Jira Product Discovery and Confluence. Jira rated the incident major; it started at 2026-03-10 00:06 UTC and was resolved at 2026-03-10 00:59 UTC, lasting 52 min. A hotfix restored automation performance while the backlog was processed.

Jira reported a major incident involving increased API error rates in Jira and Jira Service Management Ecosystem Apps, starting 2026-02-12 10:44 UTC and lasting 6 days 21 h. Forge and Connect apps were unaffected. The vendor ran a restoration process for affected apps and resolved permission errors across all Apps; the incident was resolved at 2026-02-19 08:04 UTC.

Jira reported a critical outage affecting Jira and JSM access for some users in us-east-1, with connection failures and unavailable services. It started at 2026-02-06 20:24 UTC and was resolved at 2026-02-07 05:38 UTC, lasting 9 h 13 min; mitigation efforts included initiating a point-in-time recovery.

A critical outage prevented some users in us-east-1 from accessing Jira and JSM, starting 2026-02-05 14:13 UTC and resolving 2026-02-05 21:38 UTC, lasting 7 h 25 min. Jira placed affected sites in maintenance mode to expedite resolution; services returned to normal for all affected customers.

Jira reported a major partial service disruption affecting issue creation, viewing, editing, and board viewing for some customers. It started at 2026-01-12 18:23 UTC and was resolved at 2026-01-12 23:45 UTC, lasting 5 h 21 min; Jira confirmed services were operating normally for all impacted customers.

A major incident prevented some Automation for Jira rules from executing in Jira and Jira Service Management in Asia Pacific and South East regions; other regions were unaffected. It started 2026-01-06 05:18 UTC and was resolved 2026-01-07 11:32 UTC, lasting 30 h 14 min. New events were fixed, and failed rules were rerun by replaying historical events.

Jira reported a critical incident affecting outbound email, mobile push notifications, and support ticket delivery across cloud products, recorded from 2025-12-27 04:42 UTC to 2025-12-27 05:20 UTC (37 min). The postmortem reports email and notification failures beginning at 02:48 UTC, triggered by expired monitoring-infrastructure TLS certificates; core Jira and Confluence remained available, and affected services were restored.