Confluence Status

All Systems Operational

About This Site

Here we will post updates about Confluence's service availability. For status information about other Atlassian products or services, please visit the Atlassian status page.

View Content Operational

Create and Edit Operational

Comments Operational

Authentication and User Management Operational

Search Operational

Administration Operational

Notifications Operational

Marketplace Apps Operational

Mobile Operational

iOS App Operational

Android App Operational

Purchasing & Licensing Operational

Signup Operational

Confluence Automations Operational

Cloud to Cloud Migrations - Copy Product Data Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Feb 16, 2024

No incidents reported today.

Feb 15, 2024

No incidents reported.

Feb 14, 2024

Service Disruptions Affecting Atlassian Products

Resolved - We experienced increased errors on Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, Compass, and Atlassian Analytics. The issue has been resolved and the services are operating normally.
Feb 14, 23:32 UTC

Monitoring - We have identified the root cause of the Service Disruptions affecting all Atlassian products and have mitigated the problem. We are now monitoring this closely.
Feb 14, 22:55 UTC

Identified - We have identified the root cause of the increased errors and have mitigated the problem. We continue to work on resolving the issue and monitoring this closely.
Feb 14, 22:31 UTC

Investigating - We are investigating reports of intermittent errors for all Cloud Customers across all Atlassian products. We will provide more details once we identify the root cause.
Feb 14, 21:57 UTC

Feb 13, 2024

No incidents reported.

Feb 12, 2024

Service Disruptions Affecting Confluence Cloud

Resolved - Between February 9, 4 PM UTC to February 12, 5:49 PM UTC, we experienced degraded performance related to Invitations on Confluence and Jira Software Cloud. The issue has been resolved and the service is operating normally.
Feb 12, 20:00 UTC

Identified - We are experiencing intermittent issues with the Invite flow for new accounts on Jira and Confluence Cloud. The team identified the issue and we are in the process of pushing the fix to all affected customers.
Feb 12, 17:11 UTC

Investigating - We are investigating cases of degraded performance/accessibility for some Confluence Cloud customers. We will provide more details within the next 2 hours.
Feb 12, 15:27 UTC

Service Disruptions Affecting Confluence

Resolved - Between 13:36 UTC to 14:36 UTC, we experienced degraded performance in Confluence Cloud. The issue has been resolved and the service is operating normally.
Feb 12, 15:07 UTC

Investigating - We are investigating cases of degraded performance/accessibility for some Confluence Cloud customers. We will provide more details within the next 2 hours.
Feb 12, 14:24 UTC

Feb 11, 2024

No incidents reported.

Feb 10, 2024

No incidents reported.

Feb 9, 2024

No incidents reported.

Feb 8, 2024

No incidents reported.

Feb 7, 2024

User searches failing

Resolved - Between 15:40 UTC to 15:57 UTC customers experienced intermittent failures when searching for users in Atlassian cloud services: Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, and Compass. The issue has been resolved and the service is operating normally.
Feb 7, 17:44 UTC

Monitoring - We have mitigated the problem. We are now monitoring closely.
Feb 7, 17:05 UTC

Investigating - We are investigating an issue with our user search service that is impacting Atlassian cloud service: Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, and Compass. We will provide more details within the next hour.
Feb 7, 16:40 UTC

Feb 6, 2024

Editing legacy pages result in the page not loading

Resolved - We experienced an issue with being able to edit legacy pages in Confluence. The issue has been resolved and the service is operating normally.
Feb 6, 23:12 UTC

Identified - We continue to work on resolving the issue with being unable to edit legacy pages in Confluence. We have identified the root cause and expect recovery shortly.
Feb 6, 22:23 UTC

Drop in the success rate of Forge hosted storage API calls

Resolved - We identified a problem with the Forge hosted storage API calls, which resulted in a drop in invocation success rates in the developer console. The impact of this incident has been mitigated and our monitoring tools confirm that the success-rate is back to the pre-incident behaviour. It impacted 16 apps according to our logs, where these apps saw a reduced success rate of storage.get API calls, as listed in https://developer.atlassian.com/platform/forge/runtime-reference/storage-api-basic.

As part of Forge's preparation to support Data Residency, Forge hosted storage has been undergoing a platform and data migration for storing app data. As part of this migration we do comparison checks for data consistency between the old and new platform. The previous incident earlier, https://developer.status.atlassian.com/incidents/9q71ytpjhbtl, had put the data on the new platform out of sync and so comparisons of the data from the old and new platform started showing failures and the migration logic retries on failures to test for consistency issues. This retry behaviour increased latency of these requests which led to 16 apps receiving an increased number of 504 timeout errors.

Checking synchronously was identified by the team as a bug and should have been async. Once the root cause was identified we moved our backing platform rollout to a previous stage. The rollout is split into several stages. The issues we were having were on our blocking stage where we make calls to both the old and new platform and wait for both to complete so we can test any performance issues in the new platform before using it as our source of truth. It was in this blocking stage where we had a bug that included waiting on comparisons when it should've been async.

To recover, we reverted back to our shadow mode stage. In this stage, all operations to the new platform are asynchronous, including comparisons that were blocking in the other stage and resulted in timeout issues and 504 errors being sent to apps. This is the state that Forge hosted storage has been in for several months without any problems.

Here is the timeline of the impact:
- On 2024-02-05 at 06:42 PM UTC, impact started with comparisons start happening on out of sync data in blocking mode
- On 2024-02-05 at 08:57 PM UTC, impact was detected to API by our monitoring systems
- On 2024-02-05 at 11:34 PM UTC, rollout to new platform was reverted to known stable state and impact ended

We will release a public incident review, PIR, here in the upcoming weeks for this and the incident that happened earlier, https://developer.status.atlassian.com/incidents/9q71ytpjhbtl. We will detail all that we can about what caused the issue, and what we are doing to prevent it from happening again.

We apologise for any inconveniences this may have caused our customers and the developer community and committed to preventing further issues with our hosted storage capability.
Feb 6, 02:40 UTC

Feb 5, 2024

No incidents reported.

Feb 4, 2024

No incidents reported.

Feb 3, 2024

No incidents reported.

Feb 2, 2024

No incidents reported.