tag:confluence.status.atlassian.com,2005:/historyConfluence Status - Incident History2024-03-19T08:48:32ZConfluencetag:confluence.status.atlassian.com,2005:Incident/202124292024-03-11T10:26:24Z2024-03-11T10:26:24ZConfluence facing access issues in certain EU Central regions<p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>10:26</var> UTC</small><br><strong>Resolved</strong> - Between 07:17 UTC to 09:00 UTC, we experienced issues with Confluence accessibility in EU central regions. The issue has been resolved and the service is operating normally</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>09:14</var> UTC</small><br><strong>Monitoring</strong> - We have resolved the recent issue with Confluence in EU central regions. Customers should now be able to log in as usual. We will continue to monitor the situation closely.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>08:17</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with access to Confluence that is impacting some Cloud customers. We will provide more details once we identify the root cause.</p>tag:confluence.status.atlassian.com,2005:Incident/201048382024-03-06T04:51:20Z2024-03-06T04:51:20ZConfiguration data discrepancies in automation rules<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>04:51</var> UTC</small><br><strong>Resolved</strong> - All the impacted customers have been contacted and all the impacted rules have been fixed. We are now marking this issue as resolved.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>14:51</var> UTC</small><br><strong>Update</strong> - We have successfully restored the majority of automation rules that were affected, but we are currently in the process of manually fixing the remaining ones. Our support team will be contacting the customers impacted by this issue to proceed with resolving their cases.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>07:42</var> UTC</small><br><strong>Update</strong> - We are continuing to restore the automation rules that were affected</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>03:16</var> UTC</small><br><strong>Update</strong> - This issue has been mitigated, and we have restored the majority of automation rules that were affected. Those rules are working as normal, including the rules that had not been modified in the last 48 hours and the rules created after the incident. The remaining rules that haven't yet been restored are cases where customers have manually updated the rules after the incident happened.<br />We are proceeding with caution to avoid overwriting these changes.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>17:29</var> UTC</small><br><strong>Update</strong> - We are continuously working on restoring the affected automation rules configuration data. At the moment the majority of the impact has already been mitigated and the team is currently focusing on a few specific outstanding scenarios. We will continue to update you as we progress.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>15:20</var> UTC</small><br><strong>Update</strong> - We are currently working on restoring the lost automation rules configuration data. The email notifications related to the automation will be addressed upon restoring the lost data. Customers can update the configurations with the Automation rules themselves, and our fix will not override those changes. We will share further updates as we progress.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>10:55</var> UTC</small><br><strong>Identified</strong> - We have identified the root cause and we are currently working on deploying fix to restore any lost configuration/rules. Next update will be provided in an hour.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>09:23</var> UTC</small><br><strong>Update</strong> - We continue to investigate the issue with the Automation rules losing configuration data that is impacting certain cloud products. We are actively working to resolve this issue as quickly as possible.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>08:24</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with the Automation rules losing configuration data that is impacting some of the Cloud products. We are actively working to resolve this issue as quickly as possible.</p>tag:confluence.status.atlassian.com,2005:Incident/201024152024-02-29T02:53:17Z2024-02-29T04:00:04ZInvestigating new product purchasing<p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>02:53</var> UTC</small><br><strong>Resolved</strong> - Between 28th Feb 2024 23:15 UTC to 29th Feb 2024 00:05 UTC, we experienced issue with new product purchasing for all products. All new sign up products have been successfully provision and confirmed issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>01:27</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with new product purchasing that is impacting for all products. Customers adding new cloud products may have experienced a long waiting page or an error page after attempting to add a product. We have mitigated the root cause and are working to resolve impact for customers who attempted to add a product during the impact period. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/200974422024-02-28T17:16:44Z2024-03-07T04:53:45ZIssue with Automation and Connect Apps<p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>17:16</var> UTC</small><br><strong>Resolved</strong> - Between ~12:15 UTC and ~ 15:20 UTC Jira Cloud Automation rules and Connect apps impersonating users were failing. We have scaled up the underlying services and confirmed we aren't observing failures anymore.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>16:24</var> UTC</small><br><strong>Identified</strong> - Starting from 13:15 UTC, Automation and Connect Apps affecting certain cloud products<br /><br />We have scaled up the underlying services and we're seeing an improvement in response times and success rates. We continue to investigate the root cause and will provide the next update by 18:00 UTC.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>15:12</var> UTC</small><br><strong>Update</strong> - We continue to investigate the issue with the Automation and Connect Apps affecting certain cloud products. We are actively working to resolve this issue as quickly as possible.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>13:41</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with Automation and Connect Apps that is impacting some Cloud products. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/200347982024-02-21T04:57:17Z2024-03-01T08:24:09ZIncreased authentication errors across multiple products<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>04:57</var> UTC</small><br><strong>Resolved</strong> - Between 2:30 UTC to 4:26 UTC, we experienced increased authentication errors for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Bitbucket. The issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>04:22</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the authentication errors and have mitigated the problem. We are now monitoring this closely and will provide further updates within the hour.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>03:41</var> UTC</small><br><strong>Investigating</strong> - We are investigating authentication issues impacting some Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/199871712024-02-14T23:32:18Z2024-02-27T05:43:39ZService Disruptions Affecting Atlassian Products<p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>23:32</var> UTC</small><br><strong>Resolved</strong> - 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.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>22:55</var> UTC</small><br><strong>Monitoring</strong> - 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.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>22:31</var> UTC</small><br><strong>Identified</strong> - 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.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>21:57</var> UTC</small><br><strong>Investigating</strong> - 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.</p>tag:confluence.status.atlassian.com,2005:Incident/199674992024-02-12T20:00:06Z2024-02-12T20:00:06ZService Disruptions Affecting Confluence Cloud<p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>20:00</var> UTC</small><br><strong>Resolved</strong> - Between February 9, 4 PM UTC to February 12, 5:49 PM UTC, we experienced degraded performance related to Invitations on Confluence and Jira Software Cloud. The issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>17:11</var> UTC</small><br><strong>Identified</strong> - We are experiencing intermittent issues with the Invite flow for new accounts on Jira and Confluence Cloud. The team identified the issue and we are in the process of pushing the fix to all affected customers.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>15:27</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance/accessibility for some Confluence Cloud customers. We will provide more details within the next 2 hours.</p>tag:confluence.status.atlassian.com,2005:Incident/199670252024-02-12T15:07:58Z2024-03-07T18:53:29ZService Disruptions Affecting Confluence<p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>15:07</var> UTC</small><br><strong>Resolved</strong> - Between 13:36 UTC to 14:36 UTC, we experienced degraded performance in Confluence Cloud. The issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>14:24</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance/accessibility for some Confluence Cloud customers. We will provide more details within the next 2 hours.</p>tag:confluence.status.atlassian.com,2005:Incident/199320432024-02-07T17:44:38Z2024-02-07T17:44:38ZUser searches failing<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:44</var> UTC</small><br><strong>Resolved</strong> - Between 15:40 UTC to 15:57 UTC customers experienced intermittent failures when searching for users in Atlassian cloud services: Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, and Compass. The issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:05</var> UTC</small><br><strong>Monitoring</strong> - We have mitigated the problem. We are now monitoring closely.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>16:40</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with our user search service that is impacting Atlassian cloud service: Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, and Compass. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/199256652024-02-06T23:12:28Z2024-02-06T23:12:28ZEditing legacy pages result in the page not loading<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>23:12</var> UTC</small><br><strong>Resolved</strong> - We experienced an issue with being able to edit legacy pages in Confluence. The issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>22:23</var> UTC</small><br><strong>Identified</strong> - We continue to work on resolving the issue with being unable to edit legacy pages in Confluence. We have identified the root cause and expect recovery shortly.</p>tag:confluence.status.atlassian.com,2005:Incident/199179612024-02-06T02:40:54Z2024-02-06T02:40:54ZDrop in the success rate of Forge hosted storage API calls<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>02:40</var> UTC</small><br><strong>Resolved</strong> - We identified a problem with the Forge hosted storage API calls, which resulted in a drop in invocation success rates in the developer console. The impact of this incident has been mitigated and our monitoring tools confirm that the success-rate is back to the pre-incident behaviour. It impacted 16 apps according to our logs, where these apps saw a reduced success rate of storage.get API calls, as listed in https://developer.atlassian.com/platform/forge/runtime-reference/storage-api-basic.<br /><br />As part of Forge's preparation to support Data Residency, Forge hosted storage has been undergoing a platform and data migration for storing app data. As part of this migration we do comparison checks for data consistency between the old and new platform. The previous incident earlier, https://developer.status.atlassian.com/incidents/9q71ytpjhbtl, had put the data on the new platform out of sync and so comparisons of the data from the old and new platform started showing failures and the migration logic retries on failures to test for consistency issues. This retry behaviour increased latency of these requests which led to 16 apps receiving an increased number of 504 timeout errors. <br /><br />Checking synchronously was identified by the team as a bug and should have been async. Once the root cause was identified we moved our backing platform rollout to a previous stage. The rollout is split into several stages. The issues we were having were on our blocking stage where we make calls to both the old and new platform and wait for both to complete so we can test any performance issues in the new platform before using it as our source of truth. It was in this blocking stage where we had a bug that included waiting on comparisons when it should've been async.<br /><br />To recover, we reverted back to our shadow mode stage. In this stage, all operations to the new platform are asynchronous, including comparisons that were blocking in the other stage and resulted in timeout issues and 504 errors being sent to apps. This is the state that Forge hosted storage has been in for several months without any problems.<br /><br />Here is the timeline of the impact:<br />- On 2024-02-05 at 06:42 PM UTC, impact started with comparisons start happening on out of sync data in blocking mode<br />- On 2024-02-05 at 08:57 PM UTC, impact was detected to API by our monitoring systems<br />- On 2024-02-05 at 11:34 PM UTC, rollout to new platform was reverted to known stable state and impact ended<br /><br />We will release a public incident review, PIR, here in the upcoming weeks for this and the incident that happened earlier, https://developer.status.atlassian.com/incidents/9q71ytpjhbtl. We will detail all that we can about what caused the issue, and what we are doing to prevent it from happening again.<br /><br />We apologise for any inconveniences this may have caused our customers and the developer community and committed to preventing further issues with our hosted storage capability.</p>tag:confluence.status.atlassian.com,2005:Incident/198730042024-01-31T06:07:22Z2024-01-31T06:07:22ZConfluence Whiteboards Beta unavailable for some customers<p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>06:07</var> UTC</small><br><strong>Resolved</strong> - We have investigated reports of Confluence Whiteboards Beta being unavailable for some customers between the times of 01/30/2024 22:44 UTC and 01/31/2024 05:22 UTC. This issue has been resolved.</p>tag:confluence.status.atlassian.com,2005:Incident/198729852024-01-31T06:03:12Z2024-01-31T06:03:12ZPerformance degradation for Forge app invocations<p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>06:03</var> UTC</small><br><strong>Resolved</strong> - At around 4am UTC, about 40 percent of Forge app invocations experienced high latency, with a portion of the requests failing, during a 15 minute time window.<br /><br />The scaling of the instances was misconfigured following a new deployment of the service, which needed manual intervention which took a few minutes to resolve the issue.<br /><br />Timeline:<br />- 2024-01-31 04:00 UTC: impact started<br />- 2024-01-31 04:03 UTC: incident detected<br />- 2024-01-31 04:15 UTC: the incident was resolved and the impact ended<br /><br />This issue is now resolved and Forge is fully operational. We apologize for any inconveniences this may have caused to our customers, partners, and our developer community.</p>tag:confluence.status.atlassian.com,2005:Incident/198342642024-01-26T02:54:07Z2024-01-31T01:25:13ZService Disruptions Affecting Confluence in Asia Pacific region<p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>02:54</var> UTC</small><br><strong>Resolved</strong> - Between 1:05 AM UTC - 1:48 AM UTC, some customers in Asia Pacific region experienced degraded performance for Confluence. The root cause was a bug in our deployment process and we also found that a previous mitigation put in place for a similar issue was not functioning as expected. These issues have been resolved and the service is now operating normally.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>02:21</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the performance degradation for Confluence in Asia Pacific region and have mitigated the problem. We are now monitoring this incident closely.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>01:34</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance for some Confluence Cloud customers. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/198320672024-01-25T20:26:10Z2024-01-25T20:26:10ZCopying legacy pages in Confluence times out<p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>20:26</var> UTC</small><br><strong>Resolved</strong> - We experienced an issue in Confluence Cloud when copying legacy pages the process would time out and display a blank page. The issue has been resolved and the service is operating normally.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>19:29</var> UTC</small><br><strong>Identified</strong> - We are working to resolve an issue in Confluence Cloud when copying legacy pages the process will time out and display a blank page. We have identified the root cause and are in the process of rolling out a fix. In the meantime, the workaround is to refresh the newly copied page, and it'll be available to edit. We will provide more details once the fix is in production.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>19:24</var> UTC</small><br><strong>Investigating</strong> - We are working to resolve an issue in Confluence Cloud when copying legacy pages the process will time out and display a blank page. We have identified the root cause and are in the process of rolling out a fix. In the meantime, the workaround is to refresh the newly copied page, and it'll be available to edit. We will provide more details once the fix is in production.</p>tag:confluence.status.atlassian.com,2005:Incident/198064772024-01-24T07:29:27Z2024-01-24T07:29:27ZHigh number of sandboxes being suspended<p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>07:29</var> UTC</small><br><strong>Resolved</strong> - All sandbox sites that were affected by this incident have been restored and are now accessible.</p><p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>05:13</var> UTC</small><br><strong>Update</strong> - Majority of sandboxes have now been restored. We are in the final stages of restoring the remaining sandbox sites.</p><p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>00:09</var> UTC</small><br><strong>Update</strong> - We've begun the bulk restoration of all affected sandboxes and will be progressively restoring access.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>21:34</var> UTC</small><br><strong>Update</strong> - A fix for a subset of customers has been deployed and validated. At this time we are continuing to work on bulk restoration of the remaining affected sites.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>17:54</var> UTC</small><br><strong>Update</strong> - We've identified a fix to restore affected sandboxes.<br />We're working to roll this out, and then we'll develop a process to apply to all affected sandboxes.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>15:33</var> UTC</small><br><strong>Identified</strong> - We have identified the root cause and rolled back the code causing the issue. We're now exploring bulk restoring effected sandboxes.<br />No data was lost.<br />As a workaround, customers can 'Restore' their sandboxes and the app should be back online.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>14:33</var> UTC</small><br><strong>Update</strong> - We continue to investigate this issue's root cause. More will be shared in the next updates.<br /><br />As a workaround, customers can 'Restore' their sandboxes and the app should be back online.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>14:24</var> UTC</small><br><strong>Investigating</strong> - We are seeing sandboxes being suspended at an anomalously high rate. The team is working on finding the root cause and restore affected sandboxes.</p>tag:confluence.status.atlassian.com,2005:Incident/198132072024-01-24T04:31:34Z2024-01-24T04:31:34ZIncident impacting Whiteboards Beta<p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>04:31</var> UTC</small><br><strong>Resolved</strong> - Between 2:45 AM UTC to 4:20 AM UTC, we experienced an incident impacting the collaboration experience for Confluence Whiteboards Beta. The issue has been resolved and the service is operating normally.</p><p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>03:45</var> UTC</small><br><strong>Identified</strong> - We are investigating an incident affecting Whiteboards Beta for Confluence Cloud impacting the real time collaboration experience.<br /><br />We have identified the root cause and are working on a fix.</p>tag:confluence.status.atlassian.com,2005:Incident/197599402024-01-19T03:10:49Z2024-01-31T01:24:37ZService Disruptions Affecting Confluence<p><small>Jan <var data-var='date'>19</var>, <var data-var='time'>03:10</var> UTC</small><br><strong>Resolved</strong> - Between 1:12 AM UTC - 2:12 AM UTC, some customers in Asia Pacific region experienced degraded performance for Confluence. The root cause was a bug in our deployment process. 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.</p><p><small>Jan <var data-var='date'>19</var>, <var data-var='time'>01:51</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance for some Confluence Cloud customers. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/197070312024-01-15T01:00:14Z2024-01-29T00:14:05ZOutage in Atlassian Intelligence functionality in multiple products<p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>01:00</var> UTC</small><br><strong>Resolved</strong> - Between 23:45 UTC to 00:30 UTC, we experienced an outage in some Atlassian Intelligence features for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, Atlas, and Compass. The issue has been resolved and the service is operating normally.</p><p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>00:47</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the increased errors and have mitigated the problem. We are now monitoring closely.</p><p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>00:31</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with Atlassian Intelligence that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/196610362024-01-12T17:13:28Z2024-01-12T17:13:28ZDelayed SCIM provisioning syncs of users and groups from Identity Providers<p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>17:13</var> UTC</small><br><strong>Resolved</strong> - We experienced degraded SCIM provisioning from external Identity Providers for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Access. The issue has been resolved and the service is operating normally.</p><p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>06:55</var> UTC</small><br><strong>Update</strong> - A fix for the bottleneck identified in the Group synchronization process for SCIM Provisioning has been made. We are seeing processing start to return to normal levels and will be monitoring over the next few hours. The team is all hands on deck to keep improving the situation.</p><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>22:36</var> UTC</small><br><strong>Update</strong> - The bottleneck in the Group synchronization process for SCIM Provisioning has seen considerable improvement due to recent changes, but it is still under work. The team is all hands on deck to keep improving the situation.</p><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>18:54</var> UTC</small><br><strong>Update</strong> - The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. The team is all hands on deck to improve the situation.</p><p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>19:56</var> UTC</small><br><strong>Update</strong> - The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.</p><p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>03:17</var> UTC</small><br><strong>Monitoring</strong> - We have identified a bottleneck in the Group synchronisation process for SCIM Provisioning. We have increased the resources allocated to the process in order to mitigate the issue. We are now monitoring the service.</p><p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>22:03</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance when SCIM provisioning users/groups for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Access Cloud customers. <br />We will provide more details shortly.</p>tag:confluence.status.atlassian.com,2005:Incident/196047842024-01-04T04:21:51Z2024-01-04T04:22:09ZConfluence Copy page Performance degration<p><small>Jan <var data-var='date'> 4</var>, <var data-var='time'>04:21</var> UTC</small><br><strong>Resolved</strong> - Between 19:03 UTC and 20:39 UTC, we experienced degraded performance accessing Confluence pages for some customers in the EU and US West region. The issue has been resolved and the service is operating normally.</p><p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>20:39</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the intermittent copy page degradation and have mitigated the problem. We are now monitoring closely.</p><p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>19:03</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance for Confluence Cloud customers in EU and US West regions. We will provide more details within the 2 hours.</p>tag:confluence.status.atlassian.com,2005:Incident/194939282023-12-21T04:21:24Z2023-12-21T04:21:24ZService Disruptions Affecting Confluence<p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>04:21</var> UTC</small><br><strong>Resolved</strong> - Between 00:00 UTC and 00:20 UTC, we experienced degraded performance accessing Confluence pages for some customers in the Asia Pacific region. The issue has been resolved and the service is operating normally.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>01:51</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the increased errors and have mitigated the problem. We are now monitoring this closely.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>01:45</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance for some Confluence Cloud customers between 00:00 and 00:20 UTC affecting the view/edit experience.. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/194712282023-12-19T03:28:15Z2023-12-28T03:24:09ZAtlassian's cross product user search service is currently degraded.<p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>03:28</var> UTC</small><br><strong>Resolved</strong> - It has been resolved. Atlassian's cross product user search is working.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>16:23</var> UTC</small><br><strong>Update</strong> - Atlassian's cross product user search service is currently healthy. Searches for users within Atlassian products are working as expected.<br />We are in the process of investigating the root cause of this incident.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>16:06</var> UTC</small><br><strong>Update</strong> - Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>16:02</var> UTC</small><br><strong>Update</strong> - Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>16:01</var> UTC</small><br><strong>Update</strong> - Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>15:04</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of intermittent errors for <SOME/ALL> Atlassian, Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details once we identify the root cause.</p>tag:confluence.status.atlassian.com,2005:Incident/192543512023-12-05T18:33:00Z2023-12-05T18:33:00ZSome customers aren't receiving email notification when exporting users from User Management<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>18:33</var> UTC</small><br><strong>Resolved</strong> - We have not observed any further complaints of this issue and believe the matter is resolved.</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>06:07</var> UTC</small><br><strong>Monitoring</strong> - We have identified some delays in the delivery of emails which should be resolved now. Customers who retried are expected to receive the exports. We are currently monitoring the situation.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>21:11</var> UTC</small><br><strong>Update</strong> - Some end users have confirmed that they are now able to receive the email to download the export file. The issue might still persist for a small number of customers and we will keep monitoring and investigating further. However, there are indications that the frequency for the issue has been reduced. We will provide further updates early next week.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>02:47</var> UTC</small><br><strong>Update</strong> - Some end users confirmed that they are now able to receive the email to download the export file. The issue still persists for some customers and we are working with them to identify and investigate this issue further.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>01:24</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases where some customers aren't receiving email notification to download the file when exporting users from User Management. We will provide more details within the next hour.</p>tag:confluence.status.atlassian.com,2005:Incident/193161742023-12-04T17:15:04Z2023-12-04T17:15:04ZEgress connectivity timing out<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>17:15</var> UTC</small><br><strong>Resolved</strong> - The systems are stable after the fix and monitoring for a specified duration</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>16:59</var> UTC</small><br><strong>Monitoring</strong> - The issue was identified and a fix implemented. We are monitoring currently.</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>16:54</var> UTC</small><br><strong>Update</strong> - 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</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>16:43</var> UTC</small><br><strong>Update</strong> - Including Atlassian Developer</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>16:33</var> UTC</small><br><strong>Identified</strong> - 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.</p>