All Systems Operational

About This Site

This page is intended for Atlassian developers. Please visit https://status.atlassian.com for the status of end-user features and services.

Uptime over the past 90 days. View historical uptime.
APIs Operational
90 days ago
99.95 % uptime
Today
Bitbucket Cloud APIs Operational
90 days ago
100.0 % uptime
Today
Confluence Cloud APIs Operational
90 days ago
99.92 % uptime
Today
Jira Cloud APIs Operational
90 days ago
99.77 % uptime
Today
Product Events ? Operational
90 days ago
100.0 % uptime
Today
User APIs Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Web Triggers Operational
90 days ago
100.0 % uptime
Today
Developer Operational
90 days ago
99.98 % uptime
Today
App Deployment Operational
90 days ago
100.0 % uptime
Today
Artifactory (Maven repository) ? Operational
90 days ago
100.0 % uptime
Today
Create and manage apps ? Operational
90 days ago
100.0 % uptime
Today
Developer documentation ? Operational
90 days ago
100.0 % uptime
Today
Forge App Installation ? Operational
90 days ago
100.0 % uptime
Today
Forge CDN (Custom UI) ? Operational
90 days ago
100.0 % uptime
Today
Forge Function Invocation Operational
90 days ago
99.72 % uptime
Today
aui-cdn.atlassian.com ? Operational
90 days ago
100.0 % uptime
Today
Forge App Logs ? Operational
90 days ago
100.0 % uptime
Today
Forge App Monitoring ? Operational
90 days ago
100.0 % uptime
Today
Developer console ? Operational
90 days ago
100.0 % uptime
Today
Forge direct app distribution ? Operational
90 days ago
100.0 % uptime
Today
Hosted storage ? Operational
90 days ago
100.0 % uptime
Today
Forge CLI Operational
90 days ago
100.0 % uptime
Today
End-user consent ? Operational
90 days ago
100.0 % uptime
Today
Forge App Alerts ? Operational
90 days ago
100.0 % uptime
Today
Marketplace ? Operational
90 days ago
99.92 % uptime
Today
App listing management ? Operational
90 days ago
99.6 % uptime
Today
App listings ? Operational
90 days ago
100.0 % uptime
Today
App pricing ? Operational
90 days ago
100.0 % uptime
Today
App submissions Operational
90 days ago
100.0 % uptime
Today
Category landing pages Operational
90 days ago
100.0 % uptime
Today
Evaluations and purchases Operational
90 days ago
100.0 % uptime
Today
In-product Marketplace and app installation (Cloud) ? Operational
90 days ago
99.94 % uptime
Today
In-product Marketplace and app installation (Server) ? Operational
90 days ago
99.94 % uptime
Today
Notifications ? Operational
90 days ago
100.0 % uptime
Today
Private listings Operational
90 days ago
99.94 % uptime
Today
Reporting APIs and dashboards ? Operational
90 days ago
99.9 % uptime
Today
Search Operational
90 days ago
100.0 % uptime
Today
Vendor management Operational
90 days ago
99.6 % uptime
Today
Vendor Home Page Operational
90 days ago
100.0 % uptime
Today
Authentication and user management Operational
90 days ago
100.0 % uptime
Today
Support Operational
90 days ago
99.91 % uptime
Today
Atlassian Support contact form Operational
Developer community ? Operational
90 days ago
99.82 % uptime
Today
Developer service desk ? Operational
Marketplace service desk ? Operational
Atlassian Support Operational
Vulnerability management [AMS] Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance
Marketplace Reports Maintenance Feb 17, 2024 03:00-17:00 UTC
We will be undergoing scheduled maintenance during this time. Partner Reporting APIs will be serving stale data.
Posted on Feb 16, 2024 - 07:42 UTC
Past Incidents
Feb 16, 2024

No incidents reported today.

Feb 15, 2024
Some apps with user search were returning an empty user list
Resolved - We have now resolved an issue where some apps across Jira and Confluence that utilized user search APIs were returning an empty user list. The impact started on Monday 11th Feb 11:30am AEDT and was resolved on Thursday 15th Feb 9:45am AEDT.
Feb 15, 00:13 UTC
Feb 14, 2024
Service Disruptions Affecting Atlassian Ecosystem Platform
Resolved - Between 2024-02-14 8.18pm UTC and 2024-02-14 10:19pm UTC, the Atlassian platform suffered an outage that affected all Ecosystem supporting services.
During this timeframe, apps will have seen intermittent failures for all operations, including lifecycle events such as app installations.

This incident has now been fully mitigated.

We apologize for any inconveniences this may have caused you, your team, and our mutual customers.
Feb 14, 23:20 UTC
HOT-107523 - High MongoDB CPU usage.
Resolved - The incident has been resolved and the App Versions History functionality is working as expected.
Feb 14, 19:56 UTC
Identified - The issue has been identified and the fix is being implemented.
Feb 14, 17:58 UTC
Investigating - We are observing a degraded performance of the Versions History page of the Marketplace Apps due to the HOT-107523. The team is investigating the issue currently.
Feb 14, 16:47 UTC
Errors while invoking forge functions for newly installed apps
Resolved - We are now marking this incident as resolved.
We apologize for any inconveniences this may have caused you, your team, and our mutual customers.
Feb 14, 02:26 UTC
Monitoring - The impact of this incident has been mitigated and our monitoring tools confirm that Forge app installations are back to normal

We will continue to monitor this for the next few hours
Feb 14, 00:04 UTC
Identified - We have identified an issue with Forge function invocation that is impacting some Atlassian Cloud customers with newly installed Forge apps.

Due to a race condition, some install events 'avi:forge:installed:app' were not delivered after the Forge app was installed on a customer Cloud site.

We estimate that a maximum of 108 apps were impacted, totaling about 1K app installations.

Timeline

2024-02-08 00:00 UTC: impact start
2024-02-12 20:00 UTC: impact detected
2024-02-13 21:00 UTC: solution identified

We have identified the root cause and are currently rolling out a fix.

We will provide another update in 1 hour
Feb 13, 21:30 UTC
Investigating - We are investigating an issue with Forge function invocation that is impacting some Atlassian Developer Cloud customers with newly installed Forge apps. We will provide more details within the next two hours.
Feb 13, 18:27 UTC
Feb 13, 2024
Confluence Cloud V2 API Encoding Issue
Resolved - Apps and consumers of any Confluence Cloud V2 APIs that sent requests containing characters that do not conform to the ISO-8859-1 character encoding standard have been incorrectly encoded and stored within Confluence.

There was no impact to requests that contained the content-type header with a charset=utf-8 directive.

As a result, apps that sent requests while the impact was ongoing might have observed unexpected encoding behaviours.

Here is the timeline of the impact:
- Between 2024-02-09 9:45 & 10:32 PM UTC: the deployment containing the issue was performed
- Between 2024-02-12 11:08 & 11:50 PM UTC, the fix was rolled out to all sites.

All requests now support UTF-8 encoding. This incident is now resolved.

We will run an internal post incident review to fully understand the chain of events that lead to this incident and implement measures to prevent re-occurrence of such incidents in future.
Feb 13, 01:48 UTC
Identified - Starting 2024-02-09 9:45 PM UTC, requests to the Confluence Cloud V2 API containing characters that do not conform to the ISO-8859-1 character encoding standard may have been incorrectly encoded and stored. Please note, the previous and correct encoding is UTF-8.
Feb 12, 20:06 UTC
Feb 12, 2024
Degraded user consent capability
Resolved - Between 7:30 and 9:30 UTC we have observed increased error rate on user consent capability (accepting consent for apps). We have found root cause (excessive traffic from one of internal services) and resolved the incident at 9:30 UTC.

This incident is now resolved. We will run internal post incident review to fully understand the chain of events that lead to this incident and implement measures to prevent re-occurrence of such incidents in future.
Feb 12, 09:52 UTC
Investigating - We are investigating incident causing degradation of user consent capability - users may see intermittent consent failures. It's affecting less that 10% of interactions.

We are continuing the investigation, and will update the status page at 10:30 UTC.
Feb 12, 09:27 UTC
Feb 11, 2024

No incidents reported.

Feb 10, 2024

No incidents reported.

Feb 9, 2024

No incidents reported.

Feb 8, 2024
Some transient Forge apps failures
Resolved - Between 8:00 AM UTC and 8:45 AM UTC, we were facing some transient issues with validating tokes that resulted in failures of Forge Apps.
Feb 8, 08:00 UTC
Feb 7, 2024

No incidents reported.

Feb 6, 2024
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
Forge Storage delete API was not removing data
Resolved - Between 05:50 UTC 2024/02/05 and 18:17 UTC 2024/02/05 the delete operation on Forge storage API does not work properly. API was returning a success response code but the data were not removed.
The issue was fixed and service is now operating properly. The impact was temporary and all the record deletion requests made by the apps are now effective.
We will release a public incident review, PIR, here in the upcoming weeks for this and the incident that happened a few hours later, https://developer.status.atlassian.com/incidents/yzt262mxycm9. We will detail all that we can about what caused the issue, and what we are doing to prevent it from happening again.
Feb 5, 04:50 UTC
Feb 4, 2024

No incidents reported.

Feb 3, 2024

No incidents reported.

Feb 2, 2024

No incidents reported.

← Incident History Powered by Atlassian Statuspage