https://approjects-vendor-status-watch.static.hf.space/v/confluence.htmlIncidents from Confluence's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/tzwj4szpgdv9confluence:2026-08-27T04:22:09.127ZThu, 27 Aug 2026 04:22:09 +0000**SUMMARY** On August 27, 2026, between 03:51 and 04:35 UTC, Atlassian customers in the Western Europe and Southeast APAC regions were unable to reach Atlassian Cloud products, including Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The event was triggered by a defective code change to the routing layer of one of our proxy fleets. This led to HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by rolling back to the previous configuration release, which put the proxy fleet into a known good state. After the proxy fleet recovered, some Jira and Confluence custohttps://stspg.io/clg93z8tmk67confluence:2026-08-25T08:42:48.035ZTue, 25 Aug 2026 08:42:48 +0000On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.https://stspg.io/4pygz54p4xstconfluence:2026-08-24T19:22:47.308ZMon, 24 Aug 2026 19:22:47 +0000On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.https://stspg.io/5yp3z7zctnh9confluence:2026-08-21T07:16:32.123ZFri, 21 Aug 2026 07:16:32 +0000On 21st Aug 2026, between 04:26 UTC and 09:33 UTC, some users may have experienced issues with macros not rendering correctly in Confluence. The issue has now been resolved and the service is operating normally for all customers.https://stspg.io/dynwn3553xy4confluence:2026-08-12T20:11:34.000ZWed, 12 Aug 2026 20:11:34 +0000On August 12, 2026 some Confluence users utilizing anonymous access via public links, may have experienced a 'Something went wrong' error message. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/0bnn93w7trp6confluence:2026-07-06T09:23:39.471ZMon, 06 Jul 2026 09:23:39 +0000## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, thttps://stspg.io/npzhdwdhc99gconfluence:2026-06-16T13:46:41.998ZTue, 16 Jun 2026 13:46:41 +0000### Summary ### On Jun 12, 2026, between 07:04 and 12:10 UTC and on Jun 16, 2026, between 12:56 and 14:35 UTC, a subset of Atlassian customers using Confluence Cloud experienced errors and degraded performance when attempting to view or edit pages. The event was triggered when a database cluster within our infrastructure stopped responding to connection close requests. This caused idle connections to accumulate rather than be released — resulting in increased memory pressure and cascading errors for users. The incident was detected by our automated monitoring within 18 minutes and mitigated by scaling database resources and redeploying, which recycled the idle connections. A permanent fix has since been developed and deployed. ### IMPACT ### The overall impact was between Juhttps://stspg.io/429x5sxfy4gjconfluence:2026-06-12T07:39:11.109ZFri, 12 Jun 2026 07:39:11 +0000### Summary On Jun 12, 2026, between 07:04 and 12:10 UTC and on Jun 16, 2026, between 12:56 and 14:35 UTC, a subset of Atlassian customers using Confluence Cloud experienced errors and degraded performance when attempting to view or edit pages. The event was triggered when a database cluster within our infrastructure stopped responding to connection close requests. This caused idle connections to accumulate rather than be released — resulting in increased memory pressure and cascading errors for users. The incident was detected by our automated monitoring within 18 minutes and mitigated by scaling database resources and redeploying, which recycled the idle connections. A permanent fix has since been developed and deployed. ### IMPACT The overall impact was between Jun 12, 2026 07:04 andhttps://stspg.io/fg4d9cksd79nconfluence:2026-06-10T06:14:02.096ZWed, 10 Jun 2026 06:14:02 +0000We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.https://stspg.io/1jdhk42rgq80confluence:2026-05-27T06:03:31.792ZWed, 27 May 2026 06:03:31 +0000Between 00:50 UTC and 07:30 UTC on 27 May 2026, some users were facing errors when attempting to view Calendars in Confluence. Our engineering team identified and resolved the underlying issue, and this incident has been fully restored.https://stspg.io/qcp0sf1kjc3wconfluence:2026-05-26T10:40:00.024ZTue, 26 May 2026 10:40:00 +0000Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.https://stspg.io/v8nbtv6h3xwrconfluence:2026-05-14T04:54:57.984ZThu, 14 May 2026 04:54:57 +0000### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes. ### **IMPACT** During the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access serviceshttps://stspg.io/b4c619vvm2plconfluence:2026-05-08T01:31:38.293ZFri, 08 May 2026 01:31:38 +0000All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15. ### **IMPACT** The primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Ahttps://stspg.io/2ypzgvkf46j6confluence:2026-04-14T12:25:17.081ZTue, 14 Apr 2026 12:25:17 +0000On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/884syppcgv0cconfluence:2026-04-13T07:29:45.536ZMon, 13 Apr 2026 07:29:45 +0000### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC. ### **IMPACT** * **Duration**: ~40 minutes \(05:49–06:29 UTC, April 13, 2026\) * **Affected regions**: US East and EU \(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\). * **Affected products**: All Atlassian cloud products requiring authentication, includinghttps://stspg.io/1kmsszd6095zconfluence:2026-04-08T05:41:18.009ZWed, 08 Apr 2026 05:41:18 +0000### Summary On April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. A configuration change increased the resources reserved for a core system component that runs on nodes in our compute platform. On a subset of clusters configured for high‑density workloads, the increased reservations exceeded available node capacity interrupting search and related experiences for affected customers. The root cause was identified and a rollback was merged at 05:42 UTC with some systems seeing recovery by 07:33 UTC**.** Core search functionality was restored approximately bhttps://stspg.io/ylgpnwlnv9bbconfluence:2026-03-12T11:42:39.659ZThu, 12 Mar 2026 11:42:39 +0000On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/s7szwxd5rqfqconfluence:2026-03-10T00:15:49.969ZTue, 10 Mar 2026 00:15:49 +0000On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/d2d12xvl1zklconfluence:2026-02-20T04:14:19.453ZFri, 20 Feb 2026 04:14:19 +0000This issue has been resolved and all services are functional.https://stspg.io/rkc1nbjg025kconfluence:2026-02-19T15:44:25.955ZThu, 19 Feb 2026 15:44:25 +0000On February 19 2026, affected Confluence Cloud users may have experienced some service disruption in AP South, APSE, APSE2, East, and Central regions. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/859zc5lrrqs9confluence:2026-02-18T10:57:38.385ZWed, 18 Feb 2026 10:57:38 +0000We have implemented the fix and the group page in the Admin Hub is now functioning as expected.https://stspg.io/452gy3xttr3jconfluence:2026-02-03T10:19:54.340ZTue, 03 Feb 2026 10:19:54 +0000Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.https://stspg.io/6gc829j8tb51confluence:2026-01-08T15:27:17.401ZThu, 08 Jan 2026 15:27:17 +0000### Summary On Jan 08, 2026 between 14:54 UTC and 16:30 UTC, Atlassian customers using Confluence Cloud product\(s\) experienced degraded service with view/edit page experiences. The event was triggered by database overload due to an unexpected large burst of traffic. The database overload was the result of a configuration change, which led to a sudden spike in database connections, which impacted a subset of customers in a single partition in the us-east region. The incident was detected within 1 minute by by automated monitoring systems and mitigated by reducing the number of web server hosts connecting to the database layer, which put Atlassian systems into a known good state. The total time to resolution was about 1 hour and 26 minutes. ### **IMPACT** The overall impact was between https://stspg.io/fz5p7klv7tj8confluence:2025-12-27T02:48:17.950ZSat, 27 Dec 2025 02:48:17 +0000### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available. The issue was triggered when **TLS certificates used by Atlassian’s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependency on monitoring path leading to service disruptions. All impacted services were fully restored by **05:20 UTC**, around **2.5 hours** after customer impact began. ### IMPACT During the impact window, customers experienced: * **Outbound product email failures** \(notifications and other product https://stspg.io/7k060kfdss8wconfluence:2025-12-15T16:26:38.964ZMon, 15 Dec 2025 16:26:38 +0000On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/ysrb4l3hwp9hconfluence:2025-12-11T01:08:43.933ZThu, 11 Dec 2025 01:08:43 +0000The rollback required to resolve this issue is now completed, and we have verified across the impacted products that App installation behaviour is now working as expected. We apologize for any inconvenience this may have caused.https://stspg.io/b9fzvq7np4ffconfluence:2025-11-21T14:55:09.138ZFri, 21 Nov 2025 14:55:09 +0000### Summary On November 21, 2025, between 13:44 and 15:16 UTC, Trello customers were intermittently unable to view and update data on their boards. Customers also may have experienced issues authenticating with Atlassian products, and creating new GitHub and Slack integrations. The event was triggered by a bug encountered in the software running our edge proxy fleet, which proxies customer traffic to Atlassian cloud services. The changes included the migration of our edge proxy fleet to hosts running an ARM CPU architecture, rather than the AMD64 CPU architecture they had previously been running, which impacted US East customers. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by a scale up of of fleet size, which put Atlassian systems into ahttps://stspg.io/z7qy60bvp8x5confluence:2025-11-18T13:32:36.448ZTue, 18 Nov 2025 13:32:36 +0000Elevated Errors in Confluence Whiteboards and Databases Due to Cloudflare Outage Cloudflare successfully deployed a fix for the issue that was impacting Confluence. We are no longer seeing Confluence system performance degradation and Confluence systems have been fully restored. We will continue monitoringhttps://stspg.io/xw3xdppfjvqbconfluence:2025-11-18T02:55:17.386ZTue, 18 Nov 2025 02:55:17 +0000Our team has been able to confirm that customers should no longer be experiencing the error while attempting to edit using Confluence. We apologize for any inconvenience this may have caused. This issue is now resolved.https://stspg.io/qbfz3hs0wyx6confluence:2025-11-03T16:11:55.000ZMon, 03 Nov 2025 16:11:55 +0000On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the service is operating normally for all affected customers.