outages.live
Live

Confluence

Confluence is operational

Checked 25 s ago Operational

History

90 days agoToday

Incidents in 90 days

6

Days with an incident

6

Median duration

3 h 23 min

Longest incident

5 h 51 min

Components

15
View Content Operational
90 days ago5 days with an incidentToday
Create and Edit Operational
90 days ago5 days with an incidentToday
Comments Operational
90 days ago5 days with an incidentToday
Authentication and User Management Operational
90 days ago5 days with an incidentToday
Search Operational
90 days ago5 days with an incidentToday
Administration Operational
90 days ago5 days with an incidentToday
Notifications Operational
90 days ago5 days with an incidentToday
Marketplace Apps Operational
90 days ago5 days with an incidentToday
Purchasing & Licensing Operational
90 days ago5 days with an incidentToday
Signup Operational
90 days ago5 days with an incidentToday
Confluence Automations Operational
90 days ago6 days with an incidentToday
Cloud to Cloud Migrations - Copy Product Data Operational
90 days ago5 days with an incidentToday
Server to Cloud Migrations - Copy Product Data Operational
90 days ago5 days with an incidentToday

Mobile

iOS App Operational
90 days ago5 days with an incidentToday
Android App Operational
90 days ago5 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 1, 2026

Duration4 h 56 min02:55 to 07:51Job processing and scheduling is degraded affecting multiple Atlassian productsPartial outage

### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recu

Aug 27, 2026

Duration54 min04:22 to 05:16Issues accessing multiple Atlassian products in some regionsMajor outage

**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 discrete periods: - Fi

Aug 25, 2026

Duration5 h 51 min08:42 to 14:33Notifications are delayedPartial outage

On 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.

Aug 24, 2026

Duration3 h 53 min19:22 to 23:15Degraded performance of NotificationsDegraded

On 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.

Aug 21, 2026

Duration2 h 54 min07:16 to 10:10Marketplace App Macros Not Rendering in ConfluenceDegraded

On 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.

Aug 12, 2026

Duration2 h 2 min20:11 to 22:13Confluence intermittent errorsDegraded

On 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.

Follow Confluence

Your coding agent knows when Confluence is down, and tells you when a failure is theirs, not yours. You can also get Confluence incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "confluence" and tell me if Confluence has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=confluence
Slack
/feed subscribe https://outages.live/feed.xml?providers=confluence

Go from tracking outages to fixing production issues with Polylane.

Try Polylane