Confluence change history

Major job processing and scheduling degradation affected Confluence Automations and other Atlassian products across all commercial cloud regions, delaying or missing background tasks; interactive use was unaffected. The incident started at 2026-10-01 02:55 UTC and lasted 4 h 55 min. Atlassian implemented a fix and confirmed recovery, including missing SLA components and delayed notifications.

A critical outage made Confluence, Jira Cloud and Jira Service Management 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 confirmed recovery. The postmortem attributed the disruption to a defective routing-layer code change in a proxy fleet.

Confluence reported a major incident delaying email, mobile and slack notifications for Jira, JSM and Confluence, starting 2026-08-25 08:42 UTC and resolved at 2026-08-25 14:33 UTC, lasting 5 h 51 min. Teams applied corrective measures in one impacted region; the vendor confirmed normal service for all customers without specifying a cause.

Critical Jira and Confluence disruptions affected EU automation, user search and user picker. The incident ran from 2026-07-06 09:23 UTC to 2026-07-06 13:04 UTC (3 h 40 min), though the postmortem reports disruptions between 06:51 and 20:17 UTC. Identity-service database saturation was cited; fixes restored service, but outage-period data processing requests were not completed.

Confluence reported a major View Content incident: users received errors viewing Calendars on Confluence Cloud pages, starting 2026-05-27 06:03 UTC and resolved at 2026-05-27 07:48 UTC (1 h 45 min). Its final update reported user impact between 00:50 UTC and 07:30 UTC on 27 May 2026; engineers identified and resolved the underlying issue.

A critical outage disrupted access for many Confluence and Jira Cloud customers, starting 2026-05-14 04:54 UTC and resolving 2026-05-14 06:48 UTC; the recorded duration was 1 h 53 min. Atlassian attributed the disruption to a race condition in its internal deployment orchestration platform during a core identity service rollback in the us-east region.

Confluence reported a critical disruption affecting automation rules that invoke Rovo agents; some customers’ automations did not complete as expected. The incident started at 2026-04-14 12:25 UTC and was resolved at 2026-04-14 16:11 UTC, lasting 3 h 46 min. Service returned to normal; no cause or specific fix was stated.

A critical incident caused search errors in Confluence and Jira, with additional products affected. It started at 2026-04-08 05:41 UTC and lasted 6 h 2 min, resolving at 2026-04-08 11:43 UTC; some customers experienced indexing delays during recovery. The postmortem reported a broader impact window and noted a configuration change increased resources reserved for a core system component.

Confluence Cloud reported a major outage affecting certain Marketplace macros, with users seeing “Error rendering macro 'static-macro': Page loading failed.” It started at 2026-03-12 11:42 UTC and was resolved at 2026-03-13 00:26 UTC, lasting 12 h 43 min. Confluence reported deploying a fix and confirmed normal service for affected customers.

Confluence reported a major incident delaying automation events for some APAC customers, starting 2026-03-10 00:15 UTC and resolved at 2026-03-10 00:59 UTC (43 min). A hotfix restored automation performance while the backlog was processed; the vendor confirmed normal service for affected customers.

Confluence Cloud reported a major partial service disruption affecting View Content for some customers in AP South, APSE, APSE2, East, and Central. The incident started at 2026-02-19 15:44 UTC and was resolved at 2026-02-19 17:47 UTC, with a reported duration of 2 h 2 min; service returned to normal for all affected customers.

Org Admins could not click groups in Atlassian Administration, blocking adding/removing users and app access through groups. The vendor rated the incident major; it started at 2026-02-18 10:57 UTC and was resolved at 2026-02-18 11:30 UTC, lasting 32 min. A fix restored the Admin Hub group page.

A major Confluence Cloud outage affected some users in us-east-1, disrupting page viewing and editing; the incident started 2026-01-08 15:27 UTC and lasted 3 h 42 min. Atlassian attributed database overload to a configuration change and an unexpected traffic burst. Service was restored, with resolution recorded at 2026-01-08 19:09 UTC.

A critical incident affected email delivery, mobile notifications and support ticket creation across Atlassian Cloud products from 2025-12-27 02:48 UTC to 2025-12-27 05:20 UTC (2 h 32 min). Core Jira and Confluence functionality remained available. Atlassian attributed the issue to expired monitoring TLS certificates disrupting its metrics pipeline and confirmed all affected services were restored.

Confluence reported a critical incident blocking Connect on Forge app installations and potentially cloud migrations including Confluence Apps; currently installed apps were not expected to be affected. It started at 2025-12-11 01:08 UTC and resolved at 2025-12-11 04:37 UTC, lasting 3 h 28 min. A problematic change was rolled back, and app installation behavior was verified as working.

Confluence reported a critical outage causing elevated server errors in Whiteboards and Databases due to a global Cloudflare issue. It lasted 3 h 24 min, from 2025-11-18 13:32 UTC to 2025-11-18 16:57 UTC. Cloudflare deployed a fix, and Confluence confirmed systems were fully restored.

Confluence reported a major incident causing lost-connection errors for some customers editing content, starting at 2025-11-18 02:55 UTC and resolving at 2025-11-18 03:35 UTC (39 min). The team reverted a recent change suspected of causing the errors and confirmed customers should no longer encounter them.

Confluence reported a major outage in the APSE region affecting application access, Create and Edit, and View Content from 2025-10-24 06:31 UTC to 2025-10-24 09:18 UTC, lasting 2 h 47 min. The vendor addressed an issue causing increased database load and confirmed full recovery in the affected AP SouthEast region.

Confluence reported a major incident starting 2025-09-22 05:09 UTC, resolved at 2025-09-22 07:17 UTC (2 h 7 min). Customers experienced connection errors preventing access to atlassian.net sites; the postmortem reports intermittent errors until 06:17 UTC. Atlassian attributed the disruption to a faulty CDN configuration change, which it rolled back.

Confluence reported major intermittent Forge app invocation failures affecting smart links and scheduled triggers, with errors reported from 5:44 am UTC to 7:44 am UTC. The archived incident started 2025-07-10 08:32 UTC and resolved 2025-07-10 08:55 UTC (22 min). Mitigations reduced errors, and all scheduled triggers were replayed.

A major outage started at 2025-06-25 09:38 UTC and was resolved at 2025-06-25 10:57 UTC, lasting 1 h 19 min. Customers encountered errors loading Users and Groups pages in Atlassian Administration and errors affecting user IDP syncing. Atlassian said it mitigated the problem but did not disclose the root cause.

A major incident involved Forge invocation errors affecting a subset of marketplace apps for some Confluence, Jira Service Management, Jira, and Atlassian Developer Cloud customers in the Singapore region. Recorded start: 2025-06-10 21:41 UTC; resolved: 2025-06-10 22:34 UTC; computed duration: 52 min. The vendor reported normal service and ongoing monitoring.

Confluence reported major degradation causing email delivery delays. The incident started at 2025-06-04 17:17 UTC and was resolved at 2025-06-04 20:59 UTC, lasting 3 h 41 min; the vendor separately reported an impact window from 2025-06-04 14:11 UTC to 20:18 UTC and confirmed normal service was restored.

Confluence reported a critical Administration outage: users received 403 errors when accessing Administration. The incident started at 2025-05-27 06:53 UTC and was resolved at 2025-05-27 07:56 UTC, lasting 1 h 3 min; the vendor confirmed normal service for all affected customers but stated no cause or specific fix.

Confluence’s major outage affected Smart Answers in Search and AI Definitions for all Confluence Cloud Atlassian Intelligence customers; Rovo was unaffected. Tracked from 2025-05-06 01:11 UTC until resolution at 2025-05-06 05:55 UTC (4 h 44 min), it was fixed via rollout; the vendor reported actual impact from 2025/05/03 21:38 UTC to 2025/05/06 05:26 UTC.