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.

APIs Operational
90 days ago
99.66 % uptime
Today
Bitbucket Cloud APIs Operational
90 days ago
99.97 % uptime
Today
Confluence Cloud APIs Operational
90 days ago
99.97 % uptime
Today
Jira Cloud APIs Operational
90 days ago
97.91 % uptime
Today
Product Events ? Operational
90 days ago
99.77 % 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.79 % uptime
Today
App Deployment Operational
90 days ago
99.63 % 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
99.74 % uptime
Today
Forge CDN (Custom UI) ? Operational
90 days ago
100.0 % uptime
Today
Forge Function Invocation Operational
90 days ago
98.25 % 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
99.99 % uptime
Today
Forge direct app distribution ? Operational
90 days ago
99.95 % uptime
Today
Hosted storage ? Operational
90 days ago
99.7 % 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.75 % uptime
Today
App listing management ? Operational
90 days ago
100.0 % uptime
Today
App listings ? Operational
90 days ago
100.0 % uptime
Today
App pricing ? Operational
90 days ago
99.97 % 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
99.97 % uptime
Today
In-product Marketplace and app installation (Cloud) ? Operational
90 days ago
99.97 % uptime
Today
In-product Marketplace and app installation (Server) ? Operational
90 days ago
100.0 % uptime
Today
Notifications ? Operational
90 days ago
100.0 % uptime
Today
Private listings Operational
90 days ago
100.0 % uptime
Today
Reporting APIs and dashboards ? Operational
90 days ago
96.65 % uptime
Today
Search Operational
90 days ago
100.0 % uptime
Today
Vendor management Operational
90 days ago
100.0 % 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
100.0 % uptime
Today
Atlassian Support contact form Operational
Developer community ? Operational
90 days ago
100.0 % 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.
Past Incidents
Dec 5, 2022
Update - A new announcement post in the developer community will be posted with the next scheduled maintenance window when this becomes available, and a new Statuspage scheduled maintenance communication will be created with the same components.
Dec 5, 02:17 UTC
Completed - The scheduled maintenance has been completed.
Dec 5, 02:00 UTC
Update - The scheduled maintenance for app installations was not performed and will be rescheduled at a later date. There has not been any impact on the previously listed operations.
Dec 5, 02:00 UTC
Scheduled - Atlassian will be undergoing scheduled maintenance on 04/12/2022 from 00:00AM until 00:30AM UTC

During this time you won’t be able to:

- Install/uninstall apps
- Upgrade existing app installations
- Grant/revoke access for apps

Expect to see the above operations fail with 500 status code.

We will continue to provide updates as we progress and when you can expect these services to be restored.

Dec 1, 06:17 UTC
Resolved - This incident has been resolved.
Dec 5, 01:15 UTC
Update - We are continuing to monitor for any further issues.
Dec 5, 01:13 UTC
Update - The scheduled maintenance for app installations was not performed and will be rescheduled at a later date. There has not been any impact to the previously listed operations.

A new announcement post in the developer community will be posted with next scheduled maintenance window when this becomes available, and a statuspage will be created with the same components.

Dec 5, 01:10 UTC
Monitoring - For 15 minutes between 2022-11-28T16:14 and 2022-11-28T16:31 UTC some Forge apps failed to load due to degradation of Forge Storage API. Users may have noticed timeout errors while loading / interacting with Forge apps that utilise Storage API.

Timeline:
2022-11-28T16:14 UTC impact started
Storage API requests became slow due to blocked Node.js event loop resulting in many requests exceeding the maximum HTTP response time.
This saturated all EC2 instances with a high volume of concurrent HTTP requests.
These instances were automatically recycled after which normal operation resumed.
2022-11-28T16:31 UTC impact stopped

Current status: monitoring
As a precaution, we have temporarily increased the service capacity to mitigate further impact. We will continue to monitor the system to ensure actions taken have addressed the root cause.

Nov 30, 03:38 UTC
Dec 4, 2022

No incidents reported.

Dec 3, 2022

No incidents reported.

Dec 2, 2022
Resolved - Between 2022-12-01 23:00 UTC and 2022-12-02 11:10 UTC Forge custom fields modules did not render and they were not accessible on the issue view.

We have rolled back the change that introduced the incident.

The impact of this incident has been mitigated and our monitoring tools confirm that the module is back to the operational state.

Timeline of the impact:

2022-12-01 23:00 UTC: the code with an error was deployed to production Jira
2022-12-01 23:35 UTC: the team started getting failure alerts
2022-12-02 11:10 UTC: fix was deployed, there should be no more customer impact

We are now marking this incident as resolved.

We apologize for any inconveniences this may have caused you, your team, and our mutual customers. We are committed to finding and preventing the root cause of the issue.

Dec 2, 12:14 UTC
Identified - Starting from 2022-12-01 23:00 UTC forge custom fields modules did not render and they were not accessible on the Jira issue view.

Timeline of the impact:

2022-12-01 23:00 UTC: the code with an error was deployed to production Jira
2022-12-01 23:35 UTC: the team started getting failure alerts

To resolve the issue, we are rolling back the faulty deployment and the forge custom fields modules will resume their normal behaviour within approximately 1 hour.

We will provide another update by 2022-12-02 13:00 UTC.

Dec 2, 11:27 UTC
Dec 1, 2022
Resolved - Between 2022-11-30 23:00 UTC and 2022-12-01 13:00 UTC Forge custom fields modules did not render and they were not accessible on the issue view.

We have rolled back the change that introduced the incident.

The impact of this incident has been mitigated and our monitoring tools confirm that the module is back to the operational state.

Timeline of the impact:

2022-11-30 23:00 UTC: the code with an error was deployed to production Jira
2022-11-30 23:26 UTC: the team started getting failure alerts
2022-12-01 13:00 UTC: the change was rolled back, there should be no more customer impact.

We are now marking this incident as resolved.

We apologize for any inconveniences this may have caused you, your team, and our mutual customers. We are committed to finding and preventing the root cause of the issue.

Dec 1, 15:19 UTC
Nov 30, 2022
Nov 29, 2022
Resolved - Impact
The Jira Cloud APIs were unavailable due to an incident with Jira Cloud affecting Jira Service Management, Jira Software and Jira Work Management.

The impact to the developer platform was limited to Jira apps or apps that integrate with the Jira Cloud API with active installations on sites in the US region. As this incident impacted the availability of Jira itself, Jira apps were also unavailable. For non-jira apps running in the affected region, any calls made to the Jira Cloud API would have received HTTP 500 responses during the incident timeframe.

Timeline
Impacted started: 2022-11-28 13:03 UTC
4 RDS instances in US region were saturated (CPU utilisation)
Affected users received 500 errors when trying to load Jira (including Jira apps)
Affected apps received 500 errors when trying to call Jira Cloud APIs

Current status
Impacted ended 2022-11-28 16:07 UTC
The team has scaled out all 4 RDSes.
The impact to Jira Cloud and Jira Cloud API in the US region is now mitigated and service is fully restored.

We thank you for your patience while this situation unfolded. Our engineering team is currently monitoring these services to ensure they remain available while they continue to investigate the root cause and generate action plans to ensure this type of failure doesn’t reoccur in future.

Nov 29, 00:29 UTC
Monitoring - The issue has been identified and the impact mitigated. We're monitoring the results.
Nov 28, 16:37 UTC
Investigating - We are seeing elevated error rates with calls to the Jira API. We're investigating the issue.
Nov 28, 15:28 UTC
Nov 28, 2022
Nov 27, 2022

No incidents reported.

Nov 26, 2022

No incidents reported.

Nov 25, 2022
Resolved - We have identified the root cause of the missing query parameter values in Assets issue panel Connect module and fixed it. The impact started 2022-11-22 01.54 UTC with a gradual rollout and was fixed on 2022-11-25 15.00 UTC.
Nov 25, 15:27 UTC
Investigating - We have identified a problem with missing query parameters values in Assets Issue Panel module. We are currently investigating the root cause and will provide next update at 16:00 UTC.
Nov 25, 14:39 UTC
Nov 24, 2022

No incidents reported.

Nov 23, 2022
Resolved - Between 2022-11-17 08:50 UTC to 2022-11-23 12:30 UTC , "addonName" and “lastUpdated“ fields was incorrectly updated for 6 Marketplace partners ,resulting in inaccurate reporting data in their licenses and transactions Marketplace reports.

We will be reaching out to the 6 Marketplace partners directly and communicate the same.

The root cause has been identified and fixed, the impact of this incident has been mitigated and we confirm the “addonName” and “lastUpdated” field data is corrected and is accurate for all the 6 impacted partners.

Marketplace partner reporting UI, APIs and CSV exports across licenses and transactions Marketplace reports should render accurate data for all the 6 Marketplace partner now.

We are now marking this incident as resolved.

We apologise for the inconveniences this may have caused you. We are committed to preventing the root cause of the issue.

Nov 23, 12:43 UTC
Identified - We have identified an issue impacting App name (add-on name) in marketplace partner reporting UI, APIs and CSV exports across licenses and transactions Marketplace reports.

From our initial investigation 6 marketplace partners have been impacted and below is the impact:

* 6 App names across the impacted partners have been updated owing a glitch I.e, “lastUpdated“ and “addonName“ fields was incorrectly updated resulting in inaccurate reporting data  from 17th of November.

Workaround:
We recommend you to rely on “addonKey“ and not “addonName“ until the issue is fixed.

We will be reaching out to the impacted partners directly.

We are in the process of finding the root cause , we will share next update in ~5 hours

Nov 23, 08:53 UTC
Resolved - Our monitoring systems detected latency issues and failures on our Pricing API's for a span of 50minutes (8.22am UTC - 9.10am UTC) affecting new app purchases and paid app upgrades.

This was caused due to a faulty release in one of our internal systems.

We have now rolled back the faulty change and the issue has now been resolved.

Nov 23, 10:42 UTC
Investigating - We are currently investigating this issue.
Nov 23, 09:04 UTC
Postmortem - Read details
Dec 3, 00:35 UTC
Resolved - Between 19:39 UTC and 21:25 UTC an issue with our networking services caused an outage of a number of Ecosystem capabilities.
The impact of this incident has been mitigated and our monitoring tools confirm that the impact is resolved.
During the incident, the following capabilities were impacted:

Forge:
- 1.62% of product triggers / async events failed to be delivered during the incident window. These events have since been replayed. This means that some events may have been received out-of-order.
- Other types of Forge function invocations were not impacted.
- End-User Consent: Some end users may not have been able to view or complete the consent flow during the incident. This impacted 3.6% of requests in the incident window.
- App installation: No impact.

Atlassian Connect:
- User impersonation for Atlassian Connect apps was also impacted, 7.8% of requests to retrieve bearer tokens from the Atlassian authentication server at https://oauth-2-authorization-server.services.atlassian.com failed.

OAuth 2.0 (3LO):
- A small number of Refresh Token Rotation requests failed (0.523%). These should have recovered on subsequent retries by the client.
- A small number of Authorization Code grant flows failed (0.75%). These should have recovered on subsequent retries by the user.

Product APIs:
- Product APIs and webhooks were intermittently unreliable for impacted sites during the incident timeframe.

All affected products and platform components are now back online and no further impact has been observed.

UTC 07:23 23/11/2022 UPDATE: Added OAuth 2.0 (3LO) and Product API impact observed during the same incident timeframe.

Nov 23, 00:19 UTC
Investigating - We are currently investigating an incident impacting multiple Atlassian products (see related incidents on https://status.atlassian.com). This incident also impacts apps, and some developer and platform capabilities.

We will provide additional updates and more specific details as they become available.

Nov 22, 22:34 UTC
Nov 22, 2022
Resolved - The AMS ticket attribution issue has been resolved.
Nov 22, 17:06 UTC
Identified - The issue has been identified and a fix is being implemented.
Nov 21, 18:39 UTC
Nov 21, 2022
Resolved - We have identified the transactions causing the difference between partner reporting and remittance report for October'22/November'22. There are ~19 partners that are impacted. We will be reaching out to these partners directly.

The reporting difference was caused by a daylight savings time time change taking place at the month end.

Please note, this reporting difference has no financial impact or lost dollars.

Nov 21, 12:29 UTC
Investigating - Few partners may see discrepancy between monthly remittance report and Marketplace report due to day light savings adjustment in remittance report system.
Nov 18, 11:36 UTC