Critical impactResolvedCollaboration

Confluence outage: Issues accessing multiple Atlassian products in some regions

Confluence reported this critical-impact incident on its official status page on Aug 27, 2026, 04:22 UTC. It was resolved after 54 min.

Right now Confluence is operational. Live Confluence status →

🔔 Get alerted when Confluence has issuesFree · email alerts · no credit card
Aug 27, 2026, 04:22 UTC
started
Aug 27, 2026, 05:16 UTC
resolved
54 min
duration
Critical
impact

Affected components

  • Administration
  • Android App
  • Authentication and User Management
  • Cloud to Cloud Migrations - Copy Product Data
  • Comments
  • Confluence Automations
  • Create and Edit
  • Marketplace Apps
  • Notifications
  • Purchasing & Licensing
  • Search
  • Server to Cloud Migrations - Copy Product Data
  • Signup
  • View Content
  • iOS App
  1. postmortemSep 7, 2026, 02:53 UTC

    **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 customers (regardless of location) received HTTP 503 errors between 04:33 and 04:53 UTC as server fleets adjusted to the influx of traffic. **IMPACT** The overall impact was split into two discre

  2. resolvedAug 27, 2026, 05:16 UTC

    On 27 August 2026 UTC, Atlassian products including Jira Cloud, Jira Service Management and Confluence experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers. A public postmortem for this incident will be made available on this page when our full investigation of the incident has been completed.

  3. monitoringAug 27, 2026, 04:51 UTC

    The issues relating to loading Jira Cloud, Jira Service Management and Confluence are now in recovery. We'll continue to monitor closely to confirm stability and provide an update within one hour, or sooner as more information becomes available.

  4. identifiedAug 27, 2026, 04:33 UTC

    Our teams have identified a possible fix for the issues impacting Jira Cloud, Jira Service Management and Confluence. This is now being rolled out to impacted regions and we will update within one hour, or sooner if further information is available.

  5. investigatingAug 27, 2026, 04:25 UTC

    We are investigating an issue with accessing products that is impacting Confluence, Jira Cloud and Jira Serivce Management customers. Our team is urgently investigating this issue and we will provide further details within one hour or sooner if information is available.

  6. investigatingAug 27, 2026, 04:22 UTC

    Our teams have identified this issue is also impacting Jira Service Management. We will update further as soon as possible.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluence's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Confluence have incidents?

Confluence reported 7 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 3h 40m. See Confluence's uptime and incident history

Confluence outage on Aug 27, 2026: Issues accessing multiple Atlassian products in some regions · APIStatus.watch