Is Atlassian Analytics Down Right Now? Check if there is a current outage ongoing.

All data has been restored and validated and the issue has been resolved.

All data has been restored. We are continuing to monitor as we conduct final validations on the data to ensure nothing was missed. Once all validations are completed, the incident will be marked as resolved.

Confluence data has been completely restored across all regions. Next update when the final data restoration completes.

OpsGenie data has been completely restored across all regions. Remaining data is expected to complete in the next 24 hrs. Next update will in 24 hrs or upon completion of the next major data restoration.

Identity data has been completely restored across all regions. Restoration of the remaining impacted data is expected to complete in the next 30 hrs. Next update will be shared in 6 hrs.

Data replays are continuing and we are seeing up-to-date data appearing in some regions. We will continue to monitor progress and update again in 6 hours or at the next major change in status.

The cause of the issue has been identified and we are working on restoring missing data. Next update will be in three hours.

We have identified an issue in our Data Lake that could potentially result in the last 6 days of data not being available in Atlassian Analytics dashboard for Identity, Atlas, Confluence entities in all regions. The root cause is identified and are working on mitigating the impacted entities. Next update will be shared in 6 hours.

We have identified an issue in our Data Lake that could potentially result in the last 6 days of data not being available in Atlassian Analytics dashboard for Identity, Atlas, Confluence entities in all regions. The root cause is identified and are working on mitigating the impacted entities. Next update will be shared in 6 hours.

Incident is resolved now, all tables are up to date

We are currently investigating the issue. We identified 5 tables which might be affected: jira_project jira_issue jira_issue_field jira_issue_status_history jira_issue_cycle_time

This incident has been resolved.

The issue has been identified, fix is deployed and is being monitored

This incident is being resolved.

We have implemented a fix and error rates have returned to normal.

We are currently investigating an issue causing elevated error rates when loading charts on dashboards.

Rollout of fix has completed and data issues have been resolved.

We are continuing to rollout the identified fix and are beginning to see the issue resolved for some customers.

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.

The issue has now been resolved

The issue has been identified and a fix is being implemented.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating reports of intermittent errors for some Atlassian Analytics Cloud customers. We will provide more details once we identify the root cause.

The incident is resolved

A fix has been made and we're monitoring it's stability

We've identified the issue and are working to deploy a fix.

We are currently investigating an issue with querying Jira data in Atlassian Analytics.

We've deployed a fix for the issue and lake connection management in Atlassian Analytics is restored to normal operation.

We've identified the problem and are working to deploy the fix.

We are currently investigating an issue with creating or editing data lake connections in Atlassian Analytics.

We've deployed a fix for the issue and lake connection operations are restored to normal operation.

We've identified the problem and are working to deploy a fix.

We are currently investigating an issue with creating or editing data lake connections in Atlassian Analytics.

This incident has been resolved.

All impacted data for all customers is now successfully restored. Closing the incident communication.

Jira, Opsgenie, and JSM tables are fixed. We are continuing to work through a few remaining issues with data in Confluence tables for a small subset of customers. Next update in 12 hours or the the issue is fully resolved.

Jira, Opsgenie, and JSM tables are fixed. We are continuing to work through a few remaining issues with data in Confluence tables for a subset of customers. Next update in 12 hours or the the issue is fully resolved.

We have remediated data issues for Jira, Opsgenie, and JSM tables. There is one outstanding issue with Confluence tables we are working to resolve. Next update in 12 hours or when the issue is fully resolved.

We are continuing to remediate data for impacted customers. Next update in 12 hours

Root cause of the issue identified and fixed. Data remediation for impacted customers is in progress. Next update in 12 hours.

Some Atlassian Analytics customers could experience partial data availability, due to a bug in data migrations across regions. Root cause is identified and we are actively working towards a fix as well as remediating impacted customer data.

We have resolved the issue and restored the ability to create and edit data lake connections in Atlassian Analytics

We are currently investigating an issue with creating or editing data lake connections in Atlassian Analytics.

This incident has been resolved.

Data is being backfilled and we are seeing progress. Goal is to have data backfilled in about an hour

We've identified a fix and are reprocessing data

We are currently investigating an issue where Opsgenie dashboards in US region are experiencing delayed data loads.

Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for Atlassian Analytics. The issue has been resolved and the service is operating normally.

We have mitigated the problem and continue looking into the root cause. The outage was between 8:08pm 03/07 UTC - 08:31pm 03/07 UTC We are now monitoring closely.

We are investigating an issue with <FUNCTIONALITY IMPACTED> that is impacting <SOME/ALL> Atlassian, Atlassian Partners, Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Atlassian Developer, Atlassian (deprecated), Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Atlassian Analytics, and Rovo Cloud customers. We will provide more details within the next hour.

### Summary On June 3rd, between 09:43pm and 10:58 pm UTC, Atlassian customers using multiple product\(s\) were unable to access their services. The event was triggered by a change to the infrastructure API Gateway, which is responsible for routing the traffic to the correct application backends. The incident was detected by the automated monitoring system within five minutes and mitigated by correcting a faulty release feature flag, which put Atlassian systems into a known good state. The first communications were published on the Statuspage at 11:11pm UTC. The total time to resolution was about 75 minutes. ### **IMPACT** The overall impact was between 09:43pm and 10:17pm UTC, with the system initially in a degraded state, followed by a total outage between 10:17pm and 10:58pm UTC. _The Incident caused service disruption to customers in all regions and affected the following products:_ * Jira Software * Jira Service Management * Jira Work Management * Jira Product Discovery * Jira Align * Confluence * Trello * Bitbucket * Opsgenie * Compass ### **ROOT CAUSE** A policy used in the infrastructure API gateway was being updated in production via a feature flag. The combination of an erroneous value entered in a feature flag, and a bug in the code resulted in the API Gateway not processing any traffic. This created a total outage, where all users started receiving 5XX errors for most Atlassian products. Once the problem was identified and the feature flag updated to the correct values, all services started seeing recovery immediately. ### **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 change did not go through our regular release process and instead was incorrectly applied through a feature flag. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Prevent high-risk feature flags from being used in production * Improve the policy changes testing * Enforcing longer soak time for policy changes * Any feature flags should go through progressive rollouts to minimize broad impact * Review the infrastructure feature flags to ensure they all have appropriate defaults * Improve our processes and internal tooling to provide faster communications to our customers We apologize to customers whose services were affected by this incident and are taking immediate steps to address the above gaps. Thanks, Atlassian Customer Support

Between 22:18 UTC to 22:56 UTC, we experienced errors for multiple Cloud products. The issue has been resolved and the service is operating normally.

We are investigating an issue with error responses for some Cloud customers across multiple products. We have identified the root cause and expect recovery shortly.

The missing data issue with the team and group tables has been fixed.

We have confirmed the team tables are fixed. The fix for the group table is still rolling out.

We have a fix for the issue and are beginning to roll it out.

We've identified the issue and are working on a fix.

We are currently investigating reports of missing data in the team and group tables.

### Summary On April 15, 2024, between 2:00 and 3:00 AM UTC, Atlassian customers using Atlassian Analytics in the us-east-1 region encountered inconsistencies when querying jira\_issue data. Subsequent investigation revealed that a bug in our workflow during an internal data migration on the Data Lake caused a backlog of migrated data to accumulate, leading to incomplete data being presented to customers. Our Data Lake monitoring system can usually identify such issues within 30 minutes, but the high volume of migrations in a short timeframe prolonged the processing time. This led to an incident escalation. The issue was resolved by scaling up infrastructure to process the backlog of data. Subsequently, additional inconsistencies in data were discovered across Account, Devops, and Jira tables. The impacted data was reinstated from the source and reprocessed into the Data Lake. Despite our team's diligent efforts, it took us longer to resolve the issue due to the extensive scale of affected data. We are taking remedial actions to enhance data quality checks, along with improving tooling for quicker recovery and progressive deployments to minimize widespread impact ### **IMPACT** Between April 15, 2024, at 02:00 AM UTC and April 20 at 21:00 PM UTC, some Atlassian Analytics customers experienced service degradation. This led to inconsistencies and incomplete data for the Account, DevOps, and Jira tables in their Atlassian Analytics dashboards. ### **ROOT CAUSE** The problem arose due to a change made to enhance the internal data partitioning structure, aimed at improving performance for upcoming features. The fundamental issue stemmed from a bug in the workflows, causing data to be presented to customers before the accumulated backlog had been processed. Consequently, users of Atlassian Analytics encountered incomplete or missing data in their dashboards. Although comprehensive testing was conducted prior to deployment in the production environment, this problem arose as an exceptional scenario when dealing with significantly larger volumes of migrated data, resulting in customers seeing the migrated data prior to the completion of data processing. Subsequent validation revealed that further inconsistencies were caused by another bug in the compaction process of raw data, resulting in the selection of incorrect versions of records. This erroneous data was utilized in the aforementioned partition update process, contributing to the inconsistencies. The solution involved replicating all affected data from the source and reprocessing it within the Data Lake. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that data inconsistencies can significantly affect your productivity. To prevent this kind of incident from happening again, we plan to focus on the following measures: * Enhance our existing data quality tests and expand their scope to identify these issues earlier. * Enhance our tools to ensure quicker recovery in similar future incidents. * Progressively deploy \(by cloud region\) our changes to minimize widespread impact. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s reliability and data accuracy. Thanks, Atlassian Customer Support

This incident has been resolved.

All data issues have been resolved and validated. Closing the updates.

Most of the DevOps data has been restored. We are continuing to monitor the pipelines, next update in 12hours.

We are continuing to monitor restoration of data in the DevOps tables. The next update will be in 8 hours.

The account, jira_issue, jira_sprint, teams, and group tables are fixed. We are continuing to address issues with the DevOps tables. The next update will be in 8 hours.

The account, jira_issue, and jira_sprint table are fixed. We are continuing to address issues with the DevOps tables, teams table, and group tables. The next update will be in 8 hours.

The account and jira_issue tables are fixed. We are also addressing partial data in a few other tables including the DevOps tables and Jira Sprint table. The next update will be in 8 hours.

Most of the data for jira_issue table is fixed in all regions. We are finalising the verifications and continuing to monitor the pipelines as an additional measure. Next update in 8 hours

We are continuing to process data to fix the jira_issue table. The next update will be in 8 hours or when the job completes, whichever comes first.

We have fixed the issue with the account table. The mitigation for the jira_issue table is still in progress. We will share the next update in 8 hours.

We have identified the root cause of the new issue and started the mitigation process. Will share an update on the progress in the next 6 hours

The data processing has completed however we have identified an additional issue and are working on a mitigation. We will share a progress update in 6 hours.

We have scaled up the infrastructure to process the backlog of data, continuing to monitor the data processing job progress. Will share update on the progress in 12 hours.

We are continuing to monitor the data processing job progress and expect to have a better estimate on completion in 4 hours. At this time, the primary impacted tables are jira_issue and account that are showing partial results for some customers.

We have applied a fix and have scaled our infrastructure to help process the backlog of data.

We have identified an issue stemming from a maintenance job that is causing issues for some tables and are working on a fix. While the jira_issue table appears the most impacted, some other tables may experience similar issues.

We are currently investigating an issue with the jira_issue table where some customers are seeing partial results when querying data via Atlassian Analytics.

This incident has been resolved.

We've fixed the ability to create and edit data lake connections in Atlassian Analytics. We are monitoring to ensure there are no further issues.

We are currently investigating an issue with creating or editing data lake connections in Atlassian Analytics.

The issue is now resolved and we are closing the incident.

We have rolled out a fix for the partial jira_issue results and are monitoring the system.

We have identified the issue and are rolling out a fix for the partial results in the jira_issue table.

We are investigating an issue with the jira_issue table showing partial results.

No further issues have been identified and Jira ingestion is operating as expected. We are closing this incident as fixed.

The issue causing ingestion delays in the US region has been fixed and the data delays addressed. We will continuing to monitor the ingestion jobs as an additional measure and provide an update in the next 12 hours

We have implemented a fix and are seeing significant improvements in data ingestion speed for Jira data into the Data Lake. There will be some lingering delays as the data ingestion jobs catch up, which should be resolved in the next 14 hours.

We have identified an issue ingesting Jira data in a single US region that is impacting Atlassian Analytics dashboards and are working on a fix.

We are currently investigating an issue causing delays ingesting Jira data into the Data Lake.

This incident is now resolved.

All data is up to date and the confluence_page table should be showing accurate results. We are monitoring to ensure there are no lingering issues.

We've rolled out the fix and are reloading data over the last several hours to ensure tables are up to date. Once that reload is complete, we will close the incident. The next update will be provided in 2 hours or when the reload concludes, whichever comes first.

We've started rolling out the fix and expect to see improvement over the next hour.

We are continuing to work on the fix for this issue.

We have identified an issue with the confluence_page table. Users querying this table will see incomplete results. We are now working on deploying a fix for the issue.

This incident has been resolved.

We are seeing improved query success metrics and are monitoring the system to ensure full recovery.

We have identified the issue and are working on a resolution.

We are investigating elevated query failures when loading dashboards on Atlassian Analytics.

### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery, Opsgenie, StatusPage, and Trello. As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names used for internal service-to-service connections. Active domain names were incorrectly deleted during this event. This impacted all cloud customers across all regions. The issue was identified and resolved through the rollback of the faulty deployment to restore the domain names and Atlassian systems to a stable state. The time to resolution was two hours and 58 minutes. ### **IMPACT** External customers started reporting issues with Atlassian cloud products at 20:52 UTC. The impact of the failed change led to performance degradation or in some cases, complete service disruption. Symptoms experienced by end-users were unsuccessful page loads and/or failed interactions with our cloud products. ### **ROOT CAUSE** As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names that were being used for internal service-to-service connections. Active domain names were incorrectly deleted during this operation. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. The detection was delayed because existing testing & monitoring focused on service health rather than the entire system’s availability. To prevent a recurrence of this type of incident, we are implementing the following improvement measures: * Canary checks to monitor the entire system availability. * Faster rollback procedures for this type of service impact. * Stricter change control procedures for infrastructure modifications. * Migration of all DNS records to centralised management and stricter access controls on modification to DNS records. 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

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.

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.

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.

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.

We have not seen any errors since the fix was rolled out and are closing this incident as resolved.

We have rolled out a fix and are monitoring the results.

The issue has been identified and a fix is being implemented

We are currently investigating the issue

We can confirm the issue is now resolved and are closing the incident.

We have identified the issue and implemented a fix that should resolve the intermitted chart loading failures. We are now monitoring the recovery.

We are investigating an issue causing intermittent chart loading failures on Atlassian Analytics. Will provide more updates in an hour

The systems are stable after the fix and monitoring for a specified duration

The issue was identified and a fix implemented. We are monitoring currently.

We are currently investigating an incident that result in outbound connections from Atlassian cloud in us-east-1 intermittently timing out. This affects Jira, Trello, Confluence, Ecosystem products. The features affected for these products are those that require opening a connection from Atlassian Cloud to public endpoints on the Internet

Including Atlassian Developer

We are currently investigating an incident that result in connection time outs on service egress proxy. This affects Jira, JSM, Confluence, BitBucket, Trello, Ecosystem products. The features affected for these products are those that require a connection to service egress.

We have identified and fixed the issue causing the delay. The data ingestion jobs are processing as expected and the Opsgenie data is back to normal.

We are continuing to investigate the issue and speed up data processing jobs. Will provide further updates in the next 24 hours

We are continuing to investigate the issue and speed up data processing jobs. We will provide more details as they are available in the next 12 hours.

We are continuing to investigate the issue. While we look for the root cause of the slowness, we are also pursuing various solutions to speed up ingestion. We will provide more details in 4 hours.

We are investigating an issue causing delays ingesting Opsgenie data into the Atlassian Data Lake. We will provide more details in the next 4 hours.

### **SUMMARY** On November 11, 2023, between 9:07 and 10:03 UTC, customers using Atlassian Analytics were unable to view charts on their dashboards. The event was triggered by a routine upgrade of a database cluster used by the service responsible for querying the data used in Atlassian Analytics charts. The incident was detected within 10 minutes by our monitoring system and mitigated by redeploying the impacted services which put affected Atlassian systems into a known good state. The total time to resolution was about 56 minutes. ### **IMPACT** The overall impact was between 9:07 UTC and 10:03 UTC on November 11, 2023. The incident caused a service disruption for all customers using Atlassian Analytics during the outage window. More specifically, the service responsible for querying data to populate charts experienced errors leading to failures when viewing and creating charts. ### **ROOT CAUSE** The issue was triggered by a routine upgrade of a database cluster which caused an unexpected loss of connectivity with the service responsible for issuing queries for Atlassian Analytics. Investigation during the incident identified that this was due to the database cluster changing the IP address after the upgrade. The service did not react to this change in an expected manner ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we design our services to be highly available and resilient to most failures, this scenario was not handled as expected. We are prioritizing the following actions to avoid repeating this type of incident: * Implement more robust automatic database failure recovery. * Improve existing and implement new monitoring processes in order to detect similar issues faster. * Improve our internal documentation to more quickly resolve similar issues. 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

Simple Between 09:05 UTC to 10:00 UTC, we experienced charts failing to load for Atlassian Analytics. The issue has been resolved and the service is operating normally. Detailed Between 09:05 UTC to 10:00 UTC, all customers experienced charts failing to load for Atlassian Analytics. The root cause was a upstream update that caused database connectivity problems. There is no impact to the Atlassian Data Lake. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we’re actively working on a permanent fix. The issue has been resolved and the service is operating normally.

We are investigating an issue with charts that is impacting Atlassian Analytics customers. We will provide more details within the next hour.

All impacted customer data restored and validated.

We are continuing to monitor data restore jobs. Next updated to be provided in 8 hours.

We are continuing to monitor for any further issues.

Issue and Project data missing for some customers in from Atlassian Analytics

Data is fixed for all impacted customers. All validations are done.

Data recovery is still in progress for few remaining impacted customers. Next update in 24 hrs

Data recovery is in progress for few remaining impacted customers. Next update in 24 hrs

Root cause is identified and fixed. Most of the impacted data has been corrected, working on fixing the remaining impacted customers. Next post in 24 hours.

We have identified the root cause of the incident and working on mitigating the impacted data and rolling out a fix. Further updates will be posted on Monday AEST.

No data accuracy issues have been reported so far but we are proactively continuing to investigate the issue. Further updates in 24 hours

We are investigating reports of intermittent accuracy issues for the Jira Issue history table for Atlassian Analytics Cloud customers. We will provide more details once we identify the root cause. We have mitigated the issue from impacting further customers.

### **SUMMARY** On August 30, 2023, between 4:07 and 5:30 UTC, some customers were unable to login to Atlassian's Cloud products using [id.atlassian.com](http://id.atlassian.com).  Logged-in users were also unable to switch accounts, change passwords, or log out. Users with existing sessions were not impacted. Between 5:32 and 6:00 UTC, traffic was incrementally restored to a previous build, mitigating the impact for users. The total time to resolution was one hour and 53 minutes. ### **IMPACT** Users were not able to login using Atlassian's shared account management system \([id.atlassian.com](http://id.atlassian.com)\). This affected users who were trying to login to the following products: Jira, Confluence, Trello, Opsgenie, mobile apps and ecosystem apps. Aside from the inability to login, there was no impact on other Atlassian products or features. ### **ROOT CAUSE** Multiple Set-Cookie headers were unintentionally modified so that only the last Set-Cookie header remained in the response to user's browsers.  The issue was caused by a change to Network Extensions within the Edge Network. As a result, users that needed a new session could not login.  Upon login, the users were redirected to login again and no session was created for them. ### **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 was not detected in Atlassian's staging environment.  End-to-end tests did not cover the use case of multiple Set-Cookie headers in the single response and therefore this bug went unnoticed. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Automated tests to be put in place to validate that cookies are not being removed from responses. * Configuration of networking extensions will be guaranteed to be identical in staging and production to ensure errors are picked up earlier. Furthermore, we typically deploy our changes progressively by cloud region to avoid broad impact, but in this case, the change was not deemed risky and was deployed to all regions. To minimize the impact of breaking changes to our environments, we will implement additional preventative measures: * Changes to network extensions in the future will use progressive rollouts. * With staging being properly utilized, errors similar to this one will not be deployed to any production environments. 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

Between 4:30AM UTC to 6:00AM UTC, we experienced issues for users attempting to login for Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Jira Product Discovery, Compass, and Atlassian Analytics. The issue has been resolved and the service is operating normally.

We are investigating reports of intermittent errors for login to Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Jira Product Discovery, Compass, and Atlassian Analytics Cloud customers. We will provide more details once we identify the root cause.

We have completed verification of the data refresh for the jira_issue and jira_status_history tables. All data inconsistency issues are resolved and we are closing the incident.

We have completed a refresh of data into the lake across all regions. The next step is to verify this refresh resolved data inconsistencies in the jira_issue and jira_status_history tables. We will provide our next update once the verification is complete.

Most of the data has been recovered in all regions for all entities and customers. We continue to monitor the Data Lake for a bit longer before closing this incident

Most of the data has been recovered in all regions for all entities and customers. We continue to monitor the Data Lake for a bit longer before closing this incident

We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 24 hours.

We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 24 hours.

We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 12 hours.

We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 12 hours.

We identified the root cause and applied a fix. There are a few selected workspaces which are yet to be refreshed. We are continuing to monitor the progress of the data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however, there are still some jobs outstanding specifically for a few customers. We will post the next update in 12 hours.

We are continuing to monitor progress of the Jira data refresh into the Atlassian Data Lake and are also investigating into performance improvements to speed up the process. The majority of data has already been refreshed, however there are still some jobs outstanding specifically for customers in a single region. We will post the next update in 6 hours.

We are continuing to monitor progress of the Jira data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however there are still some jobs outstanding specifically for customers in a single region. We will post the next update within 4 hours.

We are continuing to monitor progress of the Jira data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however there are still some jobs outstanding specifically for customers in a single region. We will post the next update within 4 hours.

We are continuing to monitor progress of the Jira data refresh into the Atlassian Data Lake. The majority of data has already been refreshed, however there are still some jobs outstanding. We will post the next update within 4 hours.

Jira refresh is complete for a few regions . We continue to monitor the progress of the job and will provide further updates once its available

The data refresh for confluence is complete . The Jira refresh is still underway and will take a few hours to catch up .

The data refresh is running and is being monitored .

We are continuing to investigate this issue.

Data is currently being refreshed across confluence and Jira issue to fix data inconsistencies .Data lag is expected during this time . We will provide more updates once the data refresh is complete and the lag is back to expected range.

From August 17th 02:02 UTC to August 21st 07:01 UTC, we experienced some Jira data becoming unavailable in the Atlassian Data Lake for Atlassian Analytics customers. The issue has been resolved and the service is operating normally.

Nearly all of the affected data has been restored to the Atlassian Data Lake and we are continuing to monitor the progress of the remaining data restoration.

Data restoration into the Atlassian Data Lake still in progress. We continue to monitor the progress of the job and will provide further updates once its available

We are continuing to monitor the jobs that are restoring data into the Atlassian Data Lake and will update with further information when it is available.

We've initiated jobs to replay the unavailable data into the data lake and we're now monitoring the progress of those jobs closely. We expect the replay to take several hours and will update with further information as it becomes available.

We are investigating cases of Jira data being unavailable in the Atlassian Data Lake for some Atlassian Analytics customers. We will provide more details once we identify the root cause.

We mitigated the issue with Sign-ups, Product Activation, and Billing, and the systems are back to BAU, and all functionality is restored.

We have identified the root cause of the Sign-ups, Product Activation, and Billing not working and have mitigated the problem. We are now monitoring closely.

We are investigating an issue with Sign-ups, Product Activation, and Billing that is impacting all of our Cloud Customers. We will provide more details within the next hour.

Between 14:00 UTC to 18:30 UTC, we experienced delays in Jira data replication into the Atlassian Data Lake for Atlassian Analytics. The issue has been resolved and the service is operating normally.

We have identified an issue that is delaying the ingestion of Jira data into the Atlassian Data Lake for a subset of Atlassian Analytics customers. The root cause has been identified and we are working to resolve the issue.

### **SUMMARY** We understand the importance of providing reliable and consistent service to our valued customers. On July 6, 2023, from 03:52 to 15:11 UTC, we experienced an issue with an upgraded version of a third-party tool that functions as our internal artifact management system. Despite our monitoring system identifying the incident within two minutes, this issue led to the degradation of the scaling capabilities of our internal hosting platform, resulting in service degradation or outages for customers of Atlassian cloud. In response to this situation, we are taking immediate measures to enhance the stability of our system and prevent similar issues from re-occurring. ### **IMPACT** This incident affected multiple regions and products due to the diminished scaling capabilities of our internal hosting platform. In most products and offerings, customers faced reduced functionality, slower response times, and limited access to specific features. ### **ROOT CAUSE** The root cause of the incident was the introduction of new functionality in a third-party tool that functions as our internal artifact management system. It led to an unexpected increase in the load on the primary database of the artifact system. Upon identifying and localizing the problem, we promptly adjusted the system configuration to regain stability. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** Over the next months, we will enact a temporary freeze on non-critical upgrades of the artifact management system, and we will focus our efforts on three high-priority initiatives: 1. **Enhancing system scaling:** We prioritized work ensuring that downtime in a critical infrastructure component does not affect the scaling of other components. We expect to complete this initiative within the next two months. 2. **Reducing interdependencies:** We are working to mitigate the risk of potential cascading failures by ensuring that significant system components are able to operate independently in the case of issues. Initiatives 1 and 2 are already in progress but have been given priority to be completed as soon as possible. 3. **Strengthening testing procedures:** Alongside these initiatives, we are addressing the need for even more stringent testing procedures than we already have in place to prevent potential issues in future updates. We are committed to collaborating closely with our technology partners to ensure the most optimal experience for our customers. We apologize for any inconvenience caused by this incident and appreciate your understanding. Our team is dedicated to continually improving our systems and processes to provide you with the exceptional service you deserve. Thank you for your continued support and trust in us. Sincerely, Atlassian Customer Support

We experienced performance issues and outages for several Atlassian Cloud Products. The issue has been resolved and the service is operating normally.

We have identified the root cause of an issue with an internal infrastructure component that has been impacting multiple Cloud products, including Jira Software, Jira Service Management and Confluence, and customers. This issue had lead to a performance impact and, in some cases, outages. We have implemented a fix to resolve the issue and recovery is in progress.

We are investigating an issue with an internal infrastructure component that is impacting multiple Cloud products, including Jira Software, Bitbucket, Jira Service Management and Confluence, and customers. These issues include performance impact and, in some cases, outages. Users may experience slow loading and uploading of attachments, login issues or inability for new customers to sign up. We have identified the root cause and are actively working on the service recovery.

Between 07:31 UTC to 12:32 UTC, we experienced errors during login for Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, Compass, and Atlassian Analytics. The issue has been resolved and the service is operating normally.

We have identified the root cause of the errors during login and have mitigated the problem. We are now monitoring closely.

We are investigating reports of errors during login that is impacting some Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, Compass, and Atlassian Analytics. We have identified the root cause and expect recovery shortly.

We are investigating reports of errors during login for some customers that is impacting some Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, and Atlassian Analytics Cloud customers. We will provide more details within the next hour.

We are investigating reports of errors during login for some customers that is impacting some Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, and Atlassian Analytics Cloud customers. We will provide more details within the next hour.

We are investigating reports of errors during login for some customers that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, and Atlassian Analytics Cloud customers. We will provide more details within the next hour.

Between 12:00 UTC to 15:00 UTC, we experienced elevated query failure rates for EU customers using Atlassian Analytics. The issue has been resolved and the service is operating normally.

We have identified the root cause of the intermittent query errors and have mitigated the problem. We are now monitoring closely.

We continue to work on resolving the query failures for Atlassian Analytics. We have identified the root cause and expect recovery shortly.

We are investigating reports of intermittent query errors for Atlassian Analytics customers. We will provide more details once we identify the root cause.

Between June 26 06:00 UTC to June 26 08:30 UTC, we experienced higher than normal query failure rates for Atlassian Analytics causing some dashboards to fail to load. The issue has been resolved and the service is operating normally.

We have identified the root cause of the intermittent errors and have mitigated the problem. We are now monitoring closely.

We are investigating an issue with Dashboards that is impacting some Atlassian Analytics Cloud customers. We will provide more details within the next hour.

Between 25/May/23 5:15 PM UTC to 25/May/23 7:56 AM UTC, the data processing infrastructure was running behind on Jira data for Atlassian Analytics. The issue has been resolved and the service is operating normally.

Our data processing infrastructure is running behind on Jira data for Atlassian Analytics. No data has been lost and the system is expected to catch up in the next few hours

Our data processing infrastructure is running behind on Jira data for Atlassian Analytics. No data has been lost and the system should be caught up within the next few hours.

Our data processing infrastructure is running behind on Jira data for Atlassian Analytics. No data has been lost and the system should be caught up within the next few hours.

We have identified the root cause of the delayed Jira data for Atlassian Analytics and mitigated the problem. We expect recovery over the next few hours as the data catches up.

We are investigating an issue with delayed Jira data in the Data Lake that is impacting all Atlassian Analytics customers. We will provide more details within the next hour.

Between 23:20 UTC to 00:10 UTC, we experienced a high query failure rate for Atlassian Analytics. The issue has been resolved and the service is operating normally.

We have identified the root cause of the failing queries and have mitigated the problem. We are now monitoring closely.

We continue to work on resolving the failing queries for Atlassian Analytics. We have identified the root cause and expect recovery shortly.

We are investigating an issue with failing queries that is impacting all Atlassian Analytics customers. We will provide more details within the next hour.

This incident has been resolved. Between 5:50 and 8:13 UTC, we experienced a table view error for Jira data in our Atlassian Analytics data lake connections. The issue has been resolved and the service is operating normally.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix was put in place.

We are investigating an issue with Jira data availability via AVP which is impacting a small number of Data Lake connections. The issue has been identified and a fix is in progress. We will provide more details within the next hour.