Atlassian Outage History
Atlassian is up right nowPingoru has recorded 1,025 incidents for Atlassian: 401 in the last 12 months and 71 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 37 | 65 of 720 (9%) |
| May 2026 | 83 | 286 of 744 (38%) |
| June 2026 | 34 | 267 of 720 (37%) |
| July 2026 | 17 | 130 of 744 (17%) |
| August 2026 | 27 | 131 of 744 (18%) |
| September 2026 | 25 | 77 of 720 (11%) |
| October 2026 | 18 | 17 of 598 (3%) |
Incidents, newest first
Notice March 3, 2025 Github integration not working – via Atlassian Compass
Started Mar 03, 2025, 09:00 AM UTC· resolved Mar 03, 2025, 09:00 AM UTC
- resolved Mar 03, 2025, 11:37 PM UTC
Compass customers using Github may have experienced intermittent problems in receiving events or leveraging features such as "config-as-code", this was due to an outage on Github
Notice February 27, 2025 Gitlab integration not working – via Atlassian Compass
Started Feb 27, 2025, 04:30 AM UTC· resolved Feb 27, 2025, 04:30 AM UTC
- resolved Feb 27, 2025, 08:43 PM UTC
Compass customers using Gitlab may have experienced intermittent problems in receiving events or leveraging features such as "config-as-code", this was due to an outage on Gitlab.
Minor February 20, 2025 Elevated error rates loading charts 38m via Atlassian Analytics· Dashboards
Started Feb 20, 2025, 12:59 PM UTC· resolved Feb 20, 2025, 01:38 PM UTC
- investigating Feb 20, 2025, 12:59 PM UTC
We are currently investigating an issue causing elevated error rates when loading charts on dashboards.
- monitoring Feb 20, 2025, 01:20 PM UTC
We have implemented a fix and error rates have returned to normal.
- resolved Feb 20, 2025, 01:38 PM UTC
This incident is being resolved.
Minor February 20, 2025 Degraded website performance for some customers. 10h 7m via Bitbucket· Website
Started Feb 20, 2025, 11:52 AM UTC· resolved Feb 20, 2025, 10:00 PM UTC
- investigating Feb 20, 2025, 11:52 AM UTC
We are currently investigating an issue impacting some customers who are seeing intermittent errors accessing the Bitbucket.org website.
- identified Feb 20, 2025, 12:57 PM UTC
We've identified an issue with some customers DNS configuration that can be blocking some Bitbucket assets. We are still investigating and will update statuspage with more information shortly.
- identified Feb 20, 2025, 02:05 PM UTC
We've identified an issue with some customers DNS configuration not resolving Atlassian domains correctly. If you are experiencing errors accessing Bitbucket, we advise allowlisting the following domains in your DNS configuration: https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/ We are still investigating the issue with vendors and will update statuspage as we learn more.
- monitoring Feb 20, 2025, 06:44 PM UTC
We have rolled out a fix for this issue and are seeing recovery for Bitbucket users. Please refresh the page and it should fix the issue. We are currently monitoring the fix and further investigating root cause.
- resolved Feb 20, 2025, 10:00 PM UTC
After monitoring, this incident is now resolved. If you continue to see issues, please ensure you are not using a stale / old tab and are loading a fresh version of Bitbucket in your browser.
Notice February 13, 2025 The Trello Desktop app is re-directing users to the home page 12h 7m via Trello· Trello.com
Started Feb 13, 2025, 03:54 PM UTC· resolved Feb 14, 2025, 04:02 AM UTC
- identified Feb 13, 2025, 03:54 PM UTC
We've identified an issue that's causing users to be re-directed to the Home page when using the Trello Desktop app. We'll provide a new update soon.
- identified Feb 13, 2025, 05:54 PM UTC
We're still working on a fix for the Trello Desktop. We'll provide a new update soon.
- identified Feb 13, 2025, 10:17 PM UTC
We're still working on a fix for the Trello Desktop. We'll provide a new update soon.
- monitoring Feb 14, 2025, 01:29 AM UTC
Our engineering team has successfully released a fix for both the MacOS and Windows Desktop Apps. To benefit from this fix, users are required to update to the latest version of the app. If you continue to experience any issues, particularly with redirection, please reach out to us through our Support channels for further assistance. Thank you for your patience and understanding as we worked to resolve this issue.
- resolved Feb 14, 2025, 04:02 AM UTC
Following a period of monitoring, we have confirmed that the issue affecting the MacOS and Windows Desktop Apps is resolved. Please update to the latest version for the latest fix. For any further issues please contact our Support team. Thank you for your patience.
Minor February 10, 2025 Jira and Confluence has degraded performance - scoped to Brazil only 1h 34m via Jira Core· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Feb 10, 2025, 05:47 PM UTC· resolved Feb 10, 2025, 07:22 PM UTC
- identified Feb 10, 2025, 05:47 PM UTC
We are investigating cases of degraded performance for Jira Work Management, Jira Service Management, and Jira Cloud customers. We are currently investigating it and will provide more details within the next 30 minutes.
- identified Feb 10, 2025, 06:07 PM UTC
We are investigating cases of degraded performance for Jira Work Management, Jira Service Management,Jira Cloud and confluence customers. We are currently investigating it and will provide more details within the next hour.
- resolved Feb 10, 2025, 07:22 PM UTC
Between February 10, 2025, at 17:04 UTC and 18:32 UTC, some customers for Jira Work Management, Jira Service Management, Jira, Jira Product Discovery Cloud and Confluence experienced degraded performance and 500 errors. We found that cloud products in Brazil encountered an internal limit with our cloud service provider. We redistributed traffic to mitigate this issue and are working with our cloud provider to address this issue in the future. The issue has been resolved and all the services are operating normally.
- postmortem Feb 26, 2025, 02:13 AM UTC
### Summary On February 10, 2025, between 16:10 and 18:35 UTC, Atlassian customers in Brazil experienced intermittent failures accessing and using Jira and Confluence Cloud. This disruption was due to our Content Delivery Network \(CDN\) not having sufficient capacity in Brazil under a certain network configuration. Changes in the lead-up to the incident included enabling CDN for Jira and Confluence in Brazil between January 20th and February 6th to improve performance and security. Jira and Confluence experience success rate monitoring detected the incident within 50 minutes. The incident was mitigated by temporarily disabling CDN in Brazil, which put Atlassian systems into a known good state. The total time to resolution was two hours and 25 minutes. ### **IMPACT** The overall impact was on February 10, 2025, between 16:10 and 18:35 UTC to Jira and Confluence Cloud_._ The incident caused service disruption to Brazilian customers when they attempted to access or use any feature of those products. Customers observed a generic error page or “HTTP 500” error presented by our CDN provider for up to a third of all requests at peak. ### **ROOT CAUSE** Our CDN is configured to present Jira and Confluence Cloud from static IP ranges dedicated to Atlassian. This configuration limited the number of edge locations servicing customer requests, causing a high concentration of connections in the Brazilian region on one edge location in particular. When daily traffic volumes in Brazil peaked on February 10, connections through the edge location to our servers encountered a capacity limit and were rejected with a HTTP 500 error. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We understand that outages impact your productivity. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Along with our CDN provider, we have already taken the following actions to avoid repeating this type of incident: * Our CDN provider has completed the rollout of the static, dedicated IP feature to all their edge locations and enabled Jira and Confluence Cloud to be served from all of them, thus moving to the intended configuration that will provide full network capacity. * We are working with our CDN provider to perform more rigorous checks of capacity and configuration for Jira and Confluence Cloud. * Our CDN provider increased the server connection limit for Jira and Confluence Cloud in all locations, further increasing capacity. * Based on the observed failure patterns, we have created additional monitoring and alerting configurations, so we will be alerted immediately if the issue reoccurs. Additionally, we are prioritizing actions to improve the detection of failures that affect a specific region. Thanks, Atlassian Customer Support
Minor February 10, 2025 Jira and Confluence has degraded performance - scoped to Brazil only 1h 34m via Jira Work Management· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Feb 10, 2025, 05:47 PM UTC· resolved Feb 10, 2025, 07:22 PM UTC
- identified Feb 10, 2025, 05:47 PM UTC
We are investigating cases of degraded performance for Jira Work Management, Jira Service Management, and Jira Cloud customers. We are currently investigating it and will provide more details within the next 30 minutes.
- identified Feb 10, 2025, 06:07 PM UTC
We are investigating cases of degraded performance for Jira Work Management, Jira Service Management,Jira Cloud and confluence customers. We are currently investigating it and will provide more details within the next hour.
- resolved Feb 10, 2025, 07:22 PM UTC
Between February 10, 2025, at 17:04 UTC and 18:32 UTC, some customers for Jira Work Management, Jira Service Management, Jira, Jira Product Discovery Cloud and Confluence experienced degraded performance and 500 errors. We found that cloud products in Brazil encountered an internal limit with our cloud service provider. We redistributed traffic to mitigate this issue and are working with our cloud provider to address this issue in the future. The issue has been resolved and all the services are operating normally.
- postmortem Feb 26, 2025, 02:13 AM UTC
### Summary On February 10, 2025, between 16:10 and 18:35 UTC, Atlassian customers in Brazil experienced intermittent failures accessing and using Jira and Confluence Cloud. This disruption was due to our Content Delivery Network \(CDN\) not having sufficient capacity in Brazil under a certain network configuration. Changes in the lead-up to the incident included enabling CDN for Jira and Confluence in Brazil between January 20th and February 6th to improve performance and security. Jira and Confluence experience success rate monitoring detected the incident within 50 minutes. The incident was mitigated by temporarily disabling CDN in Brazil, which put Atlassian systems into a known good state. The total time to resolution was two hours and 25 minutes. ### **IMPACT** The overall impact was on February 10, 2025, between 16:10 and 18:35 UTC to Jira and Confluence Cloud_._ The incident caused service disruption to Brazilian customers when they attempted to access or use any feature of those products. Customers observed a generic error page or “HTTP 500” error presented by our CDN provider for up to a third of all requests at peak. ### **ROOT CAUSE** Our CDN is configured to present Jira and Confluence Cloud from static IP ranges dedicated to Atlassian. This configuration limited the number of edge locations servicing customer requests, causing a high concentration of connections in the Brazilian region on one edge location in particular. When daily traffic volumes in Brazil peaked on February 10, connections through the edge location to our servers encountered a capacity limit and were rejected with a HTTP 500 error. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We understand that outages impact your productivity. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Along with our CDN provider, we have already taken the following actions to avoid repeating this type of incident: * Our CDN provider has completed the rollout of the static, dedicated IP feature to all their edge locations and enabled Jira and Confluence Cloud to be served from all of them, thus moving to the intended configuration that will provide full network capacity. * We are working with our CDN provider to perform more rigorous checks of capacity and configuration for Jira and Confluence Cloud. * Our CDN provider increased the server connection limit for Jira and Confluence Cloud in all locations, further increasing capacity. * Based on the observed failure patterns, we have created additional monitoring and alerting configurations, so we will be alerted immediately if the issue reoccurs. Additionally, we are prioritizing actions to improve the detection of failures that affect a specific region. Thanks, Atlassian Customer Support
Minor February 5, 2025 Jira is slow or inaccessible for some users 1d 11h via Jira Product Discovery· Open projects, Create and delete fields, Add/view data points ("Capture")
Started Feb 05, 2025, 10:44 AM UTC· resolved Feb 06, 2025, 09:45 PM UTC
- investigating Feb 05, 2025, 10:44 AM UTC
We are investigating reports of intermittent errors for some Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers.
- monitoring Feb 05, 2025, 11:10 AM UTC
We have identified the root cause of the intermittent errors and have mitigated the problem. We are now monitoring this closely.
- monitoring Feb 06, 2025, 09:33 AM UTC
We continue to monitor the mitigation measures implemented to address the intermittent errors reported.
- resolved Feb 06, 2025, 09:45 PM UTC
Between 05/Feb/25 2:30 PM UTC and 05/Feb/25 3:28 PM UTC some customers for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud experienced intermittent errors. We have identified the root cause of the intermittent errors and have mitigated the problem. The issue has been resolved and the service is operating normally.
Minor February 5, 2025 Jira is slow or inaccessible for some users 1d 11h via Jira Core· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Feb 05, 2025, 10:44 AM UTC· resolved Feb 06, 2025, 09:45 PM UTC
- investigating Feb 05, 2025, 10:44 AM UTC
We are investigating reports of intermittent errors for some Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers.
- monitoring Feb 05, 2025, 11:10 AM UTC
We have identified the root cause of the intermittent errors and have mitigated the problem. We are now monitoring this closely.
- monitoring Feb 06, 2025, 09:34 AM UTC
We continue to monitor the mitigation measures implemented to address the intermittent errors reported.
- resolved Feb 06, 2025, 09:45 PM UTC
Between 05/Feb/25 2:30 PM UTC and 05/Feb/25 3:28 PM UTC some customers for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud experienced intermittent errors. We have identified the root cause of the intermittent errors and have mitigated the problem. The issue has been resolved and the service is operating normally.
Minor February 5, 2025 Jira is slow or inaccessible for some users 1d 11h via Jira Work Management· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Feb 05, 2025, 10:44 AM UTC· resolved Feb 06, 2025, 09:45 PM UTC
- investigating Feb 05, 2025, 10:44 AM UTC
We are investigating reports of intermittent errors for some Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers.
- monitoring Feb 05, 2025, 11:10 AM UTC
We have identified the root cause of the intermittent errors and have mitigated the problem. We are now monitoring this closely.
- monitoring Feb 06, 2025, 09:34 AM UTC
We continue to monitor the mitigation measures implemented to address the intermittent errors reported.
- resolved Feb 06, 2025, 09:45 PM UTC
Between 05/Feb/25 2:30 PM UTC and 05/Feb/25 3:28 PM UTC some customers for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud experienced intermittent errors. We have identified the root cause of the intermittent errors and have mitigated the problem. The issue has been resolved and the service is operating normally.
Minor January 31, 2025 Jira Issue History data missing 1d 11h via Atlassian Analytics· Atlassian Data Lake
Started Jan 31, 2025, 08:14 PM UTC· resolved Feb 02, 2025, 07:28 AM UTC
- investigating Jan 31, 2025, 08:14 PM UTC
We are aware of an issue with missing Jira issue history data for some EU customers. We are rolling out a fix and will update once the issue is resolved.
- identified Feb 01, 2025, 12:08 AM UTC
We are continuing to rollout the identified fix and are beginning to see the issue resolved for some customers.
- resolved Feb 02, 2025, 07:28 AM UTC
Rollout of fix has completed and data issues have been resolved.
Minor January 23, 2025 Jira services are unavailable and have degraded performance in certain regions 19h 55m via Jira Core· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Jan 23, 2025, 05:29 PM UTC· resolved Jan 24, 2025, 01:24 PM UTC
- investigating Jan 23, 2025, 05:29 PM UTC
We are investigating cases of degraded performance for Jira Work Management, Jira Service Management, and Jira Cloud customers in certain regions. We will provide more details within the next hour.
- identified Jan 23, 2025, 06:17 PM UTC
We continue to work on resolving the degraded performance for Jira Work Management, Jira Service Management, and Jira. We have identified the root cause and expect recovery shortly.
- monitoring Jan 23, 2025, 06:40 PM UTC
We have mitigated the degraded performance of Jira Work Management, Jira Service Management, and Jira Cloud. We are now monitoring the situation closely.
- resolved Jan 24, 2025, 01:24 PM UTC
This incident has been resolved.
Minor January 23, 2025 Jira services are unavailable and have degraded performance in certain regions 19h 55m via Jira Work Management· Viewing content, Create and edit, Authentication and User Management, Search and 7 more
Started Jan 23, 2025, 05:29 PM UTC· resolved Jan 24, 2025, 01:24 PM UTC
- investigating Jan 23, 2025, 05:29 PM UTC
We are investigating cases of degraded performance for Jira Work Management, Jira Service Management, and Jira Cloud customers in certain regions. We will provide more details within the next hour.
- identified Jan 23, 2025, 06:17 PM UTC
We continue to work on resolving the degraded performance for Jira Work Management, Jira Service Management, and Jira. We have identified the root cause and expect recovery shortly.
- monitoring Jan 23, 2025, 06:40 PM UTC
We have mitigated the degraded performance of Jira Work Management, Jira Service Management, and Jira Cloud. We are now monitoring the situation closely.
- resolved Jan 24, 2025, 01:24 PM UTC
This incident has been resolved.
Major January 21, 2025 Bitbucket integration is experiencing a partial outage related to an ongoing incident with Bitbucket Cloud 4h 57m via Atlassian Compass· Bitbucket
Started Jan 21, 2025, 05:22 PM UTC· resolved Jan 21, 2025, 10:20 PM UTC
- investigating Jan 21, 2025, 05:22 PM UTC
Bitbucket Cloud is experiencing a major outage: https://bitbucket.status.atlassian.com/ . Compass cannot setup new integrations with BBC and is not able to process updates. Events and metrics that have already been synced from Bitbucket to Compass are not impacted.
- resolved Jan 21, 2025, 10:20 PM UTC
We have verified that the Bitbucket integration is now working as expected. Marking this incident as Resolved.
Notice January 21, 2025 Bitbucket Cloud web, api, and Pipelines service outage 8h 38m via Bitbucket· Website, API, Git via SSH, Authentication and user management and 8 more
Started Jan 21, 2025, 03:30 PM UTC· resolved Jan 22, 2025, 12:08 AM UTC
- investigating Jan 21, 2025, 03:30 PM UTC
We are investigating an issue with Bitbucket Web and Git operations that is impacting Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.
- investigating Jan 21, 2025, 03:58 PM UTC
We are still investigating an issue with Bitbucket Web and Git operations that is impacting Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.
- investigating Jan 21, 2025, 05:07 PM UTC
We are investigating an issue with saturated Bitbucket database that impacts all Bitbucket operations. We will provide more details within the next hour.
- investigating Jan 21, 2025, 05:49 PM UTC
We are investigating an issue with saturated Bitbucket database that impacts all Bitbucket operations. We will provide more details within the next 30 minutes.
- monitoring Jan 21, 2025, 06:02 PM UTC
We have identified the root cause of the database issue and have mitigated the problem. We are now monitoring closely.
- monitoring Jan 21, 2025, 07:28 PM UTC
We have identified the root cause of the database issue that impacted Bitbucket website and Git operations; this has been mitigated now. We are experiencing Pipelines degradation that we are working to resolve.
- monitoring Jan 21, 2025, 08:08 PM UTC
All Git, Web, API and Pipelines services are now operational. We are continuing to monitor database and Pipelines reliability.
- resolved Jan 22, 2025, 12:08 AM UTC
Earlier we experienced database contention on high traffic tables, which resulted in website, API, and Pipelines outages. All Bitbucket services are now operational. A full post mortem will be published.
- postmortem Jan 28, 2025, 06:13 PM UTC
### Summary On January 21, 2025, between 14:02 and 17:49 UTC, Atlassian customers using Bitbucket Cloud were unable to use the website, API, or Pipelines. The event was triggered by write contention in a high traffic database table. The incident was detected within eight minutes. We then worked to both throttle traffic and improve query performance, which allowed services to recover. The total time to resolution was about three hours and 47 minutes. ### **IMPACT** The overall impact was between 14:02 and 17:49 UTC, affecting Bitbucket Cloud. This impacted customers globally, and they were unable to use the website, APIs, or Pipelines services. Git hosting \(SSH\) was unaffected. ### **ROOT CAUSE** The issue was caused by an increase in API traffic triggering write contention on a high-traffic table, resulting in increased CPU usage and degraded database performance. This ultimately impacted the availability of core services \(web, API, and Pipelines\). ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have several testing and preventative processes in place, this specific issue wasn’t identified because the code path being triggered does not commonly experience this type of traffic. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Running additional maintenance on core database tables * Added throttling on write-heavy operations To improve service resilience and recovery time for our environments, we will implement additional preventative measures such as: * Improving database observability to isolate failures * Continuing to shard data to better distribute traffic load We apologize to customers whose services were impacted by this incident and are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Notice January 14, 2025 Services menu in Opsgenie is not responding 59m via OpsGenie
Started Jan 14, 2025, 03:48 PM UTC· resolved Jan 14, 2025, 04:47 PM UTC
- investigating Jan 14, 2025, 03:48 PM UTC
Our engineering team is actively investigating this incident and working to bring the Opsgenie service back up as quickly as possible. Users affected by this incident may notice that Services functionality is slow or completely unavailable for the web page We will update this page as we have additional information.
- identified Jan 14, 2025, 03:55 PM UTC
Our team has identified the issue with the Services page in Opsgenie and is working to fix it.
- resolved Jan 14, 2025, 04:47 PM UTC
Our engineers have been closely monitoring the platform and are declaring this incident resolved. Thank you for your patience.
Major January 9, 2025 Component field value not available 6h 8m via Jira Core· Viewing content
Started Jan 09, 2025, 09:53 PM UTC· resolved Jan 10, 2025, 04:02 AM UTC
- investigating Jan 09, 2025, 09:53 PM UTC
We have identified an incident that caused the components to disappear from the field and affected our Jira, Jira work management, and Jira Service Desk Cloud customers. As of now, we do not have a root cause for the incident. We are investigating and will post updates within the next hour.
- investigating Jan 09, 2025, 11:19 PM UTC
We are continuing to investigate why components are not appearing for some users and will provide updates as we learn more.
- resolved Jan 10, 2025, 04:02 AM UTC
Between 11:30:00 UTC on 9/Jan/25 to 2:30:00 UTC on 10/Jan/25, we experienced a problem displaying the component values in Jira, Jira Work Management and Jira Service Management for some customers. The issue has been resolved and the service is operating normally.
Major January 9, 2025 Component field value not available 6h 8m via Jira Work Management· Viewing content
Started Jan 09, 2025, 09:53 PM UTC· resolved Jan 10, 2025, 04:02 AM UTC
- investigating Jan 09, 2025, 09:53 PM UTC
We have identified an incident that caused the components to disappear from the field and affected our Jira, Jira work management, and Jira Service Desk Cloud customers. As of now, we do not have a root cause for the incident. We are investigating and will post updates within the next hour.
- investigating Jan 09, 2025, 11:19 PM UTC
We are continuing to investigate why components are not appearing for some users and will provide updates as we learn more.
- resolved Jan 10, 2025, 04:02 AM UTC
Between 11:30:00 UTC on 9/Jan/25 to 2:30:00 UTC on 10/Jan/25, we experienced a problem displaying the component values in Jira, Jira Work Management and Jira Service Management for some customers. The issue has been resolved and the service is operating normally.
Notice December 31, 2024 Increased error rate in Bitbucket cloud APIs 1d 13h via Bitbucket· API
Started Dec 31, 2024, 11:41 AM UTC· resolved Jan 02, 2025, 01:40 AM UTC
- investigating Dec 31, 2024, 11:41 AM UTC
Bitbucket Cloud support has observed a small increase in errors with all Bitbucket cloud APIs, we are investigating the issue and looking into root cause.
- monitoring Dec 31, 2024, 01:14 PM UTC
A solution has been implemented, and we're monitoring the fix to confirm resolution.
- resolved Jan 02, 2025, 01:40 AM UTC
This incident has been resolved.
Critical December 19, 2024 Gitlab integration not operational 45m via Atlassian Compass· Gitlab
Started Dec 19, 2024, 10:41 PM UTC· resolved Dec 19, 2024, 11:27 PM UTC
- investigating Dec 19, 2024, 10:41 PM UTC
We're seeing issues with the Gitlab integration, given Gitlab's ongoing issues: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/67645861f92e4e58064f7d32
- investigating Dec 19, 2024, 10:41 PM UTC
We're seeing issues with the Gitlab integration, given Gitlab's ongoing issues: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/67645861f92e4e58064f7d32
- resolved Dec 19, 2024, 11:27 PM UTC
Gitlab has mitigated the issue and we are seeing recovery and no errors during ingestion.
Minor December 18, 2024 Issues with attachments, including viewing previews, downloading and uploading 41m via Jira Core· Viewing content, Create and edit
Started Dec 18, 2024, 12:54 PM UTC· resolved Dec 18, 2024, 01:36 PM UTC
- identified Dec 18, 2024, 12:54 PM UTC
We have identified the issue and we are working to fix the issue.
- identified Dec 18, 2024, 12:58 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Dec 18, 2024, 01:13 PM UTC
A fix has been implemented and we are monitoring the result.
- resolved Dec 18, 2024, 01:36 PM UTC
This incident has been resolved.
Minor December 18, 2024 Issues with attachments, including viewing previews, downloading and uploading 41m via Jira Work Management· Viewing content, Create and edit
Started Dec 18, 2024, 12:54 PM UTC· resolved Dec 18, 2024, 01:36 PM UTC
- identified Dec 18, 2024, 12:54 PM UTC
We have identified the issue and we are working to fix the issue.
- identified Dec 18, 2024, 12:58 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Dec 18, 2024, 01:13 PM UTC
A fix has been implemented and we are monitoring the result.
- resolved Dec 18, 2024, 01:36 PM UTC
This incident has been resolved.
Minor December 18, 2024 Issues with attachments, including viewing previews, downloading and uploading 43m via Bitbucket· Git LFS
Started Dec 18, 2024, 12:51 PM UTC· resolved Dec 18, 2024, 01:35 PM UTC
- identified Dec 18, 2024, 12:51 PM UTC
We have identified the issue and we are working to fix the issue.
- identified Dec 18, 2024, 12:53 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Dec 18, 2024, 01:15 PM UTC
A fix has been implemented and we are monitoring the result.
- resolved Dec 18, 2024, 01:35 PM UTC
This incident has been resolved.
Minor December 16, 2024 Elevated 5XX errors in Schedule API at Opsgenie USA region 1h 30m via OpsGenie
Started Dec 16, 2024, 03:30 PM UTC· resolved Dec 16, 2024, 05:00 PM UTC
- resolved Dec 16, 2024, 05:18 PM UTC
Our team has identified the issue in Schedule API between 15:30 UTC and 17:00 UTC. We saw performance degradation and 5XX errors in response. Faulty deployment has been reverted quickly in the USA region and rapid recovery is seen. We are monitoring the system for a full recovery right now. The Schedule API is up and running again without any data loss.
Major December 13, 2024 INCOMPATIBLE VIEW SCHEMA CHANGE errors being encountered when attempting to query the jira_issue table 6h 16m via Atlassian Analytics· Dashboards, Atlassian Data Lake
Started Dec 13, 2024, 03:14 AM UTC· resolved Dec 13, 2024, 09:30 AM UTC
- investigating Dec 13, 2024, 03:14 AM UTC
We are investigating reports of intermittent errors for some Atlassian Analytics Cloud customers. We will provide more details once we identify the root cause.
- identified Dec 13, 2024, 04:02 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Dec 13, 2024, 04:46 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Dec 13, 2024, 05:06 AM UTC
We are continuing to monitor for any further issues.
- identified Dec 13, 2024, 05:27 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Dec 13, 2024, 09:30 AM UTC
The issue has now been resolved