Confluence Status Page

Oct 1, 2026 · resolved Oct 1

### 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: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Aug 27, 2026 · resolved Aug 27

**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: - First, on 27 August 2026, between 03:51 and 04:35 UTC on Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The incident caused service disruption to customer traffic originating from Western Europe and Southeast APAC regions, with HTTP 404 errors returned. There was no impact to customer API traffic, regardless of origin location. - Second, on 27 August 2026, between 04:33 and 04:53 UTC, some Jira and Confluence customers regardless of location received HTTP 503 errors after the HTTP 404 errors were solved: ~32% of requests in ap-southeast-2, ~4% of requests in eu-west-1, ~2.5% of requests in us-west-2 and ap-southeast-1, and <1% of requests in all remaining global regions. **ROOT CAUSE** The event was triggered by a code change to one of our proxy fleets. However, there was a defect in the code deployed which was not detected by manual and automated testing. This led to a misconfiguration of a tenant lookup functionality in the proxy tier, which led to traffic not having a valid network path, resulting in HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions. After the proxy tier impact recovered, a second period of impact was caused to some Jira and Confluence customers. Due to the reduction of traffic served to Jira and Confluence by the proxy fleet, the Jira and Confluence service tiers had automatically scaled in the number of servers serving customer traffic. Once the proxy fleet functionality was restored, the surge of traffic overwhelmed the Jira service tier, which returned an elevated rate of HTTP 503s until it automatically scaled out again. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified because the change was related to a very specific kind of edge case that was not picked up by our automated continuous deployment suites and manual test scripts. We are prioritizing the following improvement actions to help avoid repeating this type of incident: - **Adding further deployment safeguards:** The deployment pipeline for the configuration of the impacted proxy tier was using a legacy system and did not have the appropriate slow regional rollout features configured correctly. We have already added the correct safeguards, and we are moving this to our company standard deployment pipeline that includes all of our safety controls enabled by default. We are also auditing all networking services to validate that they are all on the new standard pipeline deployment service. - **Enhancing service fleet scaling policies:** The auto scaling configuration for our Jira and Confluence service fleets was configured to scale in too aggressively. We are thoroughly reviewing and updating all of the complex Jira and Confluence auto scaling policies to ensure that this doesn’t occur again. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Aug 25, 2026 · resolved Aug 25

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 · resolved Aug 24

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 · resolved Aug 21

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.

Is Confluence down right now?

No — Confluence is up. All systems operational as of Oct 12, 2:41 AM UTC.

What is Confluence's current status?

Confluence: All Systems Operational. Alert24 checks Confluence's status page continuously and can notify you the moment it changes.

How do I get alerted when Confluence goes down?

Alert24 monitors Confluence and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.