Compass Status - Incident History

Deprecated: Function get_magic_quotes_gpc() is deprecated in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 99

Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 619

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 832

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
tag:compass.status.atlassian.com,2005:/history Compass Status - Incident History 2025-10-23T11:31:20Z Compass tag:compass.status.atlassian.com,2005:Incident/26813826 2025-10-21T05:24:27Z 2025-10-21T05:24:27Z Atlassian Cloud Services impacted Oct <var data-var='date'>21</var>, <var data-var='time'>05:24</var> UTC Resolved - Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the inconvenience that this incident has caused and we will provide further information when the Post Incident Investigation has been completed.Oct <var data-var='date'>21</var>, <var data-var='time'>03:24</var> UTC Update - The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues. With regards to other Atlassian products, we continue to see recovery continuing across all impacted products and our teams are continuing to monitor as the recovery continues. We will provide further update on our recovery status within two hours.Oct <var data-var='date'>21</var>, <var data-var='time'>01:07</var> UTC Update - We continue to see recovery progressing across all impacted products as backlogged items continue to be processed. The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message. We will provide further update on our recovery status in two hours.Oct <var data-var='date'>21</var>, <var data-var='time'>00:03</var> UTC Update - Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored. The Atlassian Support portal is currently still displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message. We will provide further update on our recovery status in one hour.Oct <var data-var='date'>20</var>, <var data-var='time'>22:58</var> UTC Update - Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.Oct <var data-var='date'>20</var>, <var data-var='time'>21:26</var> UTC Update - Monitoring - We've started seeing continued product experience improvement. While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and will continue to monitor the health of AWS services and the effects on Atlassian customers. We appreciate your continued patience and remain committed to full resolution as we work through this situation. We will post our next update in two hours.Oct <var data-var='date'>20</var>, <var data-var='time'>18:38</var> UTC Monitoring - There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available. We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation.Oct <var data-var='date'>20</var>, <var data-var='time'>17:43</var> UTC Update - We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.Oct <var data-var='date'>20</var>, <var data-var='time'>17:43</var> UTC Update - We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.Oct <var data-var='date'>20</var>, <var data-var='time'>17:27</var> UTC Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.Oct <var data-var='date'>20</var>, <var data-var='time'>16:36</var> UTC Update - Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.Oct <var data-var='date'>20</var>, <var data-var='time'>16:35</var> UTC Update - Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.Oct <var data-var='date'>20</var>, <var data-var='time'>15:21</var> UTC Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.Oct <var data-var='date'>20</var>, <var data-var='time'>14:03</var> UTC Update - We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide updates every hour or sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>13:58</var> UTC Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>13:56</var> UTC Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>13:07</var> UTC Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>12:06</var> UTC Update - Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>11:07</var> UTC Update - We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>09:58</var> UTC Identified - We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience. We shall continue to share updates every hour, if not sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>09:24</var> UTC Update - We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>09:23</var> UTC Update - We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not sooner.Oct <var data-var='date'>20</var>, <var data-var='time'>08:24</var> UTC Update - Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same. We shall keep you informed of the progress every hour.Oct <var data-var='date'>20</var>, <var data-var='time'>07:56</var> UTC Investigating - We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same. We shall keep you informed of the progress every hour. tag:compass.status.atlassian.com,2005:Incident/26601393 2025-09-30T14:32:25Z 2025-09-30T14:32:25Z Delays in Opsgenie, JSM Ops and Compass Ops notifications Sep <var data-var='date'>30</var>, <var data-var='time'>14:32</var> UTC Resolved - Between 13:10 UTC to 14:00 UTC, we experienced notification delay for Jira Service Management, Opsgenie, and Compass in only EU-region. The issue has been resolved and the service is operating normally.Sep <var data-var='date'>30</var>, <var data-var='time'>14:22</var> UTC Monitoring - We have identified the root cause of the notification delay for Opsgenie, JSM Ops and Compass Ops and have mitigated the problem. We are now monitoring closely.Sep <var data-var='date'>30</var>, <var data-var='time'>14:09</var> UTC Identified - We continue to work on resolving the notification delays for Jira Service Management, Opsgenie, and Compass. We have identified the root cause and expect recovery shortly.Sep <var data-var='date'>30</var>, <var data-var='time'>14:07</var> UTC Investigating - We are observing delays in Opsgenie, JSM ops and Compass ops notification flows. No alert has been lost and our team is actively working on it to mitigate the delays. We'll keep you posted with further updates. tag:compass.status.atlassian.com,2005:Incident/26515646 2025-09-22T07:17:23Z 2025-10-01T06:24:06Z Degraded performance to multiple Atlassian experiences Sep <var data-var='date'>22</var>, <var data-var='time'>07:17</var> UTC Resolved - A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.Sep <var data-var='date'>22</var>, <var data-var='time'>06:55</var> UTC Monitoring - Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.Sep <var data-var='date'>22</var>, <var data-var='time'>05:59</var> UTC Identified - Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing. tag:compass.status.atlassian.com,2005:Incident/26475574 2025-09-21T16:30:21Z 2025-09-21T16:30:21Z Database Upgrade Sep <var data-var='date'>21</var>, <var data-var='time'>16:30</var> UTC Completed - The scheduled maintenance has been completed.Sep <var data-var='date'>21</var>, <var data-var='time'>15:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Sep <var data-var='date'>17</var>, <var data-var='time'>19:40</var> UTC Scheduled - Compass will be conducting a required database upgrade that will impact the ability to perform any write operations to Compass Component API Specifications for all users on September 21st, 2025 between 15:30 UTC and 16:30 UTC. For more information about this maintenance, please refer to the community post at: https://community.atlassian.com/forums/Compass-articles/Upcoming-Compass-Maintenance-Window/ba-p/3110106 tag:compass.status.atlassian.com,2005:Incident/26406536 2025-09-11T18:45:19Z 2025-09-11T18:45:19Z Delays observed at JSM, Opsgenie and Compass alert search functionality in US Region Sep <var data-var='date'>11</var>, <var data-var='time'>18:45</var> UTC Resolved - Between September 10, 2025, 3:19 PM UTC and September 11, 2025, 2:44 PM UTC, there was degraded performance in web experiences and the REST APIs for some Jira Service Management, Opsgenie, and Compass Cloud customers in the US region. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The issue has been resolved and the service is operating normally.Sep <var data-var='date'>11</var>, <var data-var='time'>15:05</var> UTC Monitoring - We have deployed the fix and all operations are back to normal. We will continue to monitor the operations. We will continue providing specific updates when available.Sep <var data-var='date'>11</var>, <var data-var='time'>14:00</var> UTC Update - We have progressed further in preparing our system with a probable fix. Initial testing has been successful. We are in the process of completing further testing and finalising the fix. We expect the fix to be completed in next few hours. Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass. We will continue providing specific updates when available and will ensure we have further update within the hour.Sep <var data-var='date'>11</var>, <var data-var='time'>13:02</var> UTC Update - We are progressing well with the testing of identified potential mitigation steps for this issue; and we are seeing positive early results. We will update with an ETA and further information in the next update. Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass. We will continue providing specific updates when available and will ensure we have further update within the hour.Sep <var data-var='date'>11</var>, <var data-var='time'>11:53</var> UTC Update - Atlassian teams continue to test the identified potential resolution steps for this issue. Our goal is to restore full functionality to users from Jira Service Management, Opsgenie and Compass. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.Sep <var data-var='date'>11</var>, <var data-var='time'>10:59</var> UTC Update - Our teams have are identified some potential resolution steps for this issue and continue to test the same on priority to be able to restore full functionality to users from Jira Service Management, Opsgenie and Compass. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.Sep <var data-var='date'>11</var>, <var data-var='time'>09:51</var> UTC Update - Atlassian teams continue to remain engaged with priority to restore full functionality to new alerts to users from Jira Service Management, Opsgenie and Compass. Escalation teams also continue to remain engaged on this incident to ensure our focus is not diluted from a resolution as soon as possible. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.Sep <var data-var='date'>11</var>, <var data-var='time'>08:53</var> UTC Identified - Atlassian teams remain engaged with priority to restore full functionality to new alerts to users from Jira Service Management, Opsgenie and Compass. Escalation teams are also engaged on this incident to ensure we can get to a resolution as soon as possible. At this point, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour. tag:compass.status.atlassian.com,2005:Incident/25756282 2025-07-10T08:55:10Z 2025-07-10T08:55:10Z Intermittent failure in Forge app invocation Jul <var data-var='date'>10</var>, <var data-var='time'>08:55</var> UTC Resolved - Between 10th July 5:44 am UTC to 7:44 am UTC, we experienced intermittent failure in some app funstionality(smart links, scheduled triggers) for Confluence, Jira Work Management, Jira Service Management, Jira, and Compass. The issue has been resolved and the service is operating normally. All scheduled triggers has been replayed.Jul <var data-var='date'>10</var>, <var data-var='time'>08:32</var> UTC Monitoring - We are investigating reports of intermittent errors for some Confluence, Jira Work Management, Jira Service Management, Jira, and Compass Cloud customers failing invocation, mostly scheduled triggers and smart links from 5:44 am UTC to 7:44 am UTC. We have put mitigations in place, and the errors have receded. We are monitoring the incident resolution. Customers will sometimes see errors in app functionality during this time and scheduled triggers might not work. We have replayed the scheduled triggers. tag:compass.status.atlassian.com,2005:Incident/25539713 2025-06-19T23:46:04Z 2025-06-19T23:46:04Z Degraded performance in Opsgenie and JSM operations Jun <var data-var='date'>19</var>, <var data-var='time'>23:46</var> UTC Resolved - This incident has been resolved. tag:compass.status.atlassian.com,2005:Incident/25365777 2025-06-04T20:59:00Z 2025-06-11T20:12:39Z Customers may experience delays receiving emails Jun <var data-var='date'> 4</var>, <var data-var='time'>20:59</var> UTC Resolved - Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally.Jun <var data-var='date'> 4</var>, <var data-var='time'>17:17</var> UTC Investigating - We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and mail is being processed normally as of 16:45 UTC. We will continue to monitor system performance and will provide more details within the next hour. tag:compass.status.atlassian.com,2005:Incident/25191498 2025-05-20T14:57:05Z 2025-05-20T15:41:24Z Both Compass UI and APIs are not responding May <var data-var='date'>20</var>, <var data-var='time'>14:57</var> UTC Resolved - We have verified that the incident has been resolved.May <var data-var='date'>20</var>, <var data-var='time'>14:53</var> UTC Identified - The issue has been identified and a fix is being implemented. We have put some mitigation mechanisms in place and our systems are starting to recover.May <var data-var='date'>20</var>, <var data-var='time'>14:36</var> UTC Investigating - We are currently investigating an issue impacting both the Compass UI and APIs. We are investigating this issue and will share an update once we have additional information. tag:compass.status.atlassian.com,2005:Incident/25047849 2025-05-20T04:07:31Z 2025-05-20T04:07:31Z Issues with data pipelines for customers using GitHub for Jira Connector. May <var data-var='date'>20</var>, <var data-var='time'>04:07</var> UTC Resolved - Existing events are continuing to be processed. Any updates to existing entities such as pull requests will also correct and update the data here as required. If there are any concerns about impact to your site with this connector please reach out to support and the team will address your concerns as soon as possible.May <var data-var='date'>19</var>, <var data-var='time'>01:37</var> UTC Update - Processing of previously impacted events is now underway. An update will be provided when these operations have been completed and historical processing has been completed.May <var data-var='date'>15</var>, <var data-var='time'>05:17</var> UTC Identified - Our team has identified the root cause of this issue and have reverted the change that was causing these data processing errors. All new updates from GitHub should now be flowing correctly. We are actively working to address a potential data gap for previously impacted events, and will provide an update when available.May <var data-var='date'>15</var>, <var data-var='time'>02:22</var> UTC Investigating - We are aware of an issue where users of GitHub for Jira connector may be missing pull requests and experiencing other data pipeline issues. Our team is looking into this with urgency and an update will be provided when available. tag:compass.status.atlassian.com,2005:Incident/24816399 2025-04-29T00:15:27Z 2025-04-29T00:15:27Z New components not visible when performing searches Apr <var data-var='date'>29</var>, <var data-var='time'>00:15</var> UTC Resolved - This incident has been resolved.Apr <var data-var='date'>28</var>, <var data-var='time'>20:05</var> UTC Monitoring - We've implemented a fix for this issue and are seeing systems recover. We will keep monitoring to make sure we don't see a recurrence of this issue.Apr <var data-var='date'>28</var>, <var data-var='time'>19:03</var> UTC Investigating - We're seeing a recurrence of the earlier issue around components not showing up in our search indexing. We're working on restoring the service. tag:compass.status.atlassian.com,2005:Incident/24814818 2025-04-28T17:18:40Z 2025-04-28T17:18:40Z New components not visible when performing searches Apr <var data-var='date'>28</var>, <var data-var='time'>17:18</var> UTC Resolved - This incident has been resolved.Apr <var data-var='date'>28</var>, <var data-var='time'>16:45</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Apr <var data-var='date'>28</var>, <var data-var='time'>16:01</var> UTC Identified - The issue has been identified and a fix is being implemented.Apr <var data-var='date'>28</var>, <var data-var='time'>15:43</var> UTC Investigating - We're investigating an issue around new components not being visible in search for a period of time after creation. tag:compass.status.atlassian.com,2005:Incident/24812668 2025-04-28T16:12:38Z 2025-04-28T16:12:38Z Management of Apps is partially unavailable on different platforms Apr <var data-var='date'>28</var>, <var data-var='time'>16:12</var> UTC Resolved - Between 10:55 AM UTC to 13:15 PM UTC on April 28, 2025, we experienced partial unavailability in managing Forge apps; Such as lifecycle developer console usage, and the creation and deployment of Forge apps for Atlassian Partners, Jira Work Management, Jira, Atlassian Developer, Jira Product Discovery, Compass, and Atlassian Migrations. 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.Apr <var data-var='date'>28</var>, <var data-var='time'>13:42</var> UTC Monitoring - The issues causing the unavailability of related Forge apps capabilities on multiple Atlassian platforms have been resolved, and services are now operating normally for all impacted customers. We will continue to closely monitor for stability.Apr <var data-var='date'>28</var>, <var data-var='time'>12:55</var> UTC Identified - We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms, such as apps lifecycle (installation, removals), developer console usage (including tunneling), and the creation and deployment of Forge apps. We have identified the root cause and are in the process of mitigating the impact. We'll keep you posted with further updates. Next updates in 1 hour.Apr <var data-var='date'>28</var>, <var data-var='time'>11:59</var> UTC Investigating - We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms. Such as apps lifecycle (installation, removals), developer console usage (including tunnelling), and the creation and deployment of Forge apps. Our team is working diligently to resolve this issue and restore services quickly. We are in the process of identifying the root cause and implementing the necessary fixes. Next updates in 1 hour. tag:compass.status.atlassian.com,2005:Incident/24584051 2025-04-13T06:00:21Z 2025-04-13T06:00:21Z [Scheduled Maintenance] Database Upgrade Apr <var data-var='date'>13</var>, <var data-var='time'>06:00</var> UTC Completed - The scheduled maintenance has been completed.Apr <var data-var='date'>13</var>, <var data-var='time'>05:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr <var data-var='date'> 7</var>, <var data-var='time'>01:26</var> UTC Scheduled - Compass will be conducting a required database upgrade that will impact the ability to perform any write operations to Compass for all users on April 13, 2025 between 5:00 UTC and 6:00 UTC. For more information about this maintenance, please refer to the community post - https://community.atlassian.com/forums/Compass-articles/Scheduled-maintenance-for-Compass/ba-p/2991224. tag:compass.status.atlassian.com,2005:Incident/24339288 2025-03-14T20:46:52Z 2025-03-14T20:46:52Z Some users are experiencing errors while creating new Jira and Confluence sites Mar <var data-var='date'>14</var>, <var data-var='time'>20:46</var> UTC Resolved - On March 14th, 2025, between 09:00 and 19:14 UTC, some customers experienced issues creating new sites. The errors occurring for some users during new site creation should now be resolved.Mar <var data-var='date'>14</var>, <var data-var='time'>18:54</var> UTC Investigating - We are investigating cases of errors for some users creating new sites. We will provide more details within the next hour. tag:compass.status.atlassian.com,2005:Incident/24332144 2025-03-14T03:25:32Z 2025-03-14T03:25:32Z Issues with search within Confluence and Compass Mar <var data-var='date'>14</var>, <var data-var='time'>03:25</var> UTC Resolved - Searches within Confluence and Compass should now be operating as normal. This issue will now be resolved.Mar <var data-var='date'>14</var>, <var data-var='time'>02:47</var> UTC Monitoring - Issues causing error messages when users were attempting to search within Confluence and Compass should now be resolved. Our team is monitoring ongoing performance at this time.Mar <var data-var='date'>14</var>, <var data-var='time'>02:18</var> UTC Investigating - We are aware that some users of Confluence and Compass are currently experiencing errors when attempting to search. Our team is investigating this issue with urgency and will provide an update when available. tag:compass.status.atlassian.com,2005:Incident/24254254 2025-03-06T12:51:02Z 2025-03-06T12:51:02Z Unable to load the Operations page Mar <var data-var='date'> 6</var>, <var data-var='time'>12:51</var> UTC Resolved - The issue has been resolved and the service is operating normally.Mar <var data-var='date'> 6</var>, <var data-var='time'>12:19</var> UTC Identified - We are investigating reports of the Operations page not loading for Compass Cloud customers. There is no impact to the API. We have identified the issue and are in the process of fixing it. tag:compass.status.atlassian.com,2005:Incident/24224853 2025-03-03T09:00:00Z 2025-03-03T23:37:03Z Github integration not working Mar <var data-var='date'> 3</var>, <var data-var='time'>09:00</var> UTC Resolved - 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 tag:compass.status.atlassian.com,2005:Incident/24178954 2025-02-27T04:30:00Z 2025-02-27T20:43:50Z Gitlab integration not working Feb <var data-var='date'>27</var>, <var data-var='time'>04:30</var> UTC Resolved - 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. tag:compass.status.atlassian.com,2005:Incident/24075761 2025-02-24T07:26:37Z 2025-02-24T07:26:38Z [Scheduled Maintenance] Database Upgrade Feb <var data-var='date'>24</var>, <var data-var='time'>07:26</var> UTC Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>24</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'>20</var>, <var data-var='time'>00:29</var> UTC Scheduled - Compass will be performing a database configuration update in this maintenance window. This process will reboot the database instance which has the potential to cause an outage of 5 minutes. We will update the status of the application throughout this process. tag:compass.status.atlassian.com,2005:Incident/23641968 2025-01-21T22:20:31Z 2025-01-21T22:20:31Z Bitbucket integration is experiencing a partial outage related to an ongoing incident with Bitbucket Cloud Jan <var data-var='date'>21</var>, <var data-var='time'>22:20</var> UTC Resolved - We have verified that the Bitbucket integration is now working as expected. Marking this incident as Resolved.Jan <var data-var='date'>21</var>, <var data-var='time'>17:22</var> UTC Investigating - 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. tag:compass.status.atlassian.com,2005:Incident/23264435 2024-12-19T23:27:03Z 2024-12-19T23:27:03Z Gitlab integration not operational Dec <var data-var='date'>19</var>, <var data-var='time'>23:27</var> UTC Resolved - Gitlab has mitigated the issue and we are seeing recovery and no errors during ingestion.Dec <var data-var='date'>19</var>, <var data-var='time'>22:41</var> UTC Update - We're seeing issues with the Gitlab integration, given Gitlab's ongoing issues: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/67645861f92e4e58064f7d32Dec <var data-var='date'>19</var>, <var data-var='time'>22:41</var> UTC Investigating - We're seeing issues with the Gitlab integration, given Gitlab's ongoing issues: https://status.gitlab.com/pages/incident/5b36dc6502d06804c08349f7/67645861f92e4e58064f7d32 tag:compass.status.atlassian.com,2005:Incident/23166007 2024-12-12T03:55:08Z 2024-12-12T03:55:08Z Issues accessing Compass Dec <var data-var='date'>12</var>, <var data-var='time'>03:55</var> UTC Resolved - This incident has been resolved.Dec <var data-var='date'>12</var>, <var data-var='time'>03:18</var> UTC Identified - We're seeing recovery across all of our systems. The team is still working on ensuring that impact is fully mitigated.Dec <var data-var='date'>12</var>, <var data-var='time'>02:38</var> UTC Investigating - We're seeing issues accessing the Compass application. The team is working on identifying the underlying cause. tag:compass.status.atlassian.com,2005:Incident/22265216 2024-09-24T01:07:02Z 2024-09-24T01:07:02Z Compass service inaccessible Sep <var data-var='date'>24</var>, <var data-var='time'>01:07</var> UTC Resolved - This incident has been resolved.Sep <var data-var='date'>24</var>, <var data-var='time'>00:54</var> UTC Monitoring - We've identified the issue and reverted the faulty change. We're monitoring the change propagation and are seeing systems recover across the board.Sep <var data-var='date'>24</var>, <var data-var='time'>00:41</var> UTC Investigating - We're seeing issues accessing Compass. The team has identified the issue and is currently rolling out a fix. tag:compass.status.atlassian.com,2005:Incident/22070249 2024-09-06T07:44:36Z 2024-09-06T07:44:36Z Compass Github app unavailable Sep <var data-var='date'> 6</var>, <var data-var='time'>07:44</var> UTC Resolved - This issue has now been fixed and the app is now available for ise.Sep <var data-var='date'> 6</var>, <var data-var='time'>06:32</var> UTC Identified - We have identified the issue and are working on a fix at the moment.Sep <var data-var='date'> 6</var>, <var data-var='time'>01:08</var> UTC Investigating - We are currently investigating an issue that is causing the Github app to be unavailable for some tenants.