tag:guard.status.atlassian.com,2005:/historyGuard Status - Incident History2025-05-06T20:01:38ZGuardtag:guard.status.atlassian.com,2005:Incident/246482712025-04-14T01:33:14Z2025-04-14T01:34:52ZIssues loading Administration across Atlassian Products<p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>01:33</var> UTC</small><br><strong>Resolved</strong> - Between 00:00 UTC to 01:05 UTC 14 April, users attempting to load the Administration page for Atlassian products. The issue has been resolved and the service is operating normally.</p><p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>00:40</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:guard.status.atlassian.com,2005:Incident/227312662024-11-01T05:22:45Z2024-11-01T05:22:45ZAdmin hub not responding<p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>05:22</var> UTC</small><br><strong>Resolved</strong> - Between November 1st, 02:57 AM UTC, and November 1st, 05:03 AM UTC, we experienced an issue with the Atlassian Admin hub not responding to some users. The issue has been resolved, and the service is operating normally.</p><p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>05:03</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the Atlassian Admin hub not responding and have mitigated the problem. We are now monitoring closely.</p><p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>05:01</var> UTC</small><br><strong>Identified</strong> - We continue to work on resolving the issue with the Atlassian admin hub not responding. We have identified the root cause and expect recovery shortly.</p><p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>04:37</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of intermittent errors when logging into the Atlassian admin hub at https://admin.atlassian.com. <br /><br />Once we identify the root cause, we will provide more details.</p>tag:guard.status.atlassian.com,2005:Incident/226660832024-10-25T17:23:25Z2024-10-25T17:23:25ZErrors with provisioning services<p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>17:23</var> UTC</small><br><strong>Resolved</strong> - Between 25-Oct-2024 at 9:50 AM UTC to 25-Oct-2024 at 4:52 PM UTC, we identified intermittent errors in external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that impacted all Atlassian Guard cloud customers. The issue has been resolved and the service is operating normally.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>16:16</var> UTC</small><br><strong>Update</strong> - We continue to investigate the intermittent errors in external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that are impacting all Atlassian Guard cloud customers. As the investigation proceeds, we will provide more updates.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>14:37</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate intermittent errors in external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that are impacting all Guard Cloud customers. We will provide updates as we learn more.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>13:39</var> UTC</small><br><strong>Investigating</strong> - We are again investigating intermittent errors for external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that are impacting all Guard Cloud customers. We will provide more details within the next hour.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>12:20</var> UTC</small><br><strong>Monitoring</strong> - On 25-Oct-2024 at 9:50 AM UTC, we identified intermittent errors for external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations that are impacting all Guard Cloud customers. <br /><br />We have taken action to mitigate this issue and we are now monitoring it closely.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>11:37</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of intermittent errors for external directory configuration in the admin hub (admin.atlassian.com), https://id.atlassian.com/manage-profile, and provisioning configurations, which are curerntly not loading.<br />Guard Cloud customers are affected by this issue.<br />We will provide more details once we identify the root cause.</p>tag:guard.status.atlassian.com,2005:Incident/225914302024-10-18T17:38:38Z2024-10-18T17:38:38ZSome admins unable to see some user/group memberships in AdminHub<p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>17:38</var> UTC</small><br><strong>Resolved</strong> - Between 2024-10-18 05:40 UTC-7 to 2024-10-18 08:40 UTC-7, we experienced an outage affecting user/group memberships in AdminHub for Confluence, Jira Work Management, Jira Service Management, Jira, and Guard. The issue has been resolved and the service is operating normally.</p><p><small>Oct <var data-var='date'>18</var>, <var data-var='time'>14:09</var> UTC</small><br><strong>Identified</strong> - We have received reports of intermittent errors for some Cloud customers, specifically admins who are unable to see group memberships in AdminHub. We have identified the root cause and expect recovery shortly.</p>tag:guard.status.atlassian.com,2005:Incident/219076142024-08-26T11:02:33Z2024-08-26T11:02:33ZIdentity is not syncing new user and group information<p><small>Aug <var data-var='date'>26</var>, <var data-var='time'>11:02</var> UTC</small><br><strong>Resolved</strong> - Between 02:35 UTC to 3:55 UTC on Aug 26, we experienced failing Identity sync for Jira Work Management, Jira Service Management, Jira, and Guard. The issue has been resolved and the service is operating normally. All affected Jira customers were synched with Identity and there is not need to wait 24h for a full sync.</p><p><small>Aug <var data-var='date'>26</var>, <var data-var='time'>05:33</var> UTC</small><br><strong>Monitoring</strong> - The bug has been identified and fixed. However, it could take up to 24 hours since 03:55 UTC for the User and Group reflected correctly.<br /><br />As a workaround, you may need to perform a new User or Group change.</p><p><small>Aug <var data-var='date'>26</var>, <var data-var='time'>05:29</var> UTC</small><br><strong>Investigating</strong> - Between 02:35 UTC and 03:55 UTC, due to bugs in Identity, some changes in users' and group settings were not reflected in Jira.</p>tag:guard.status.atlassian.com,2005:Incident/218299732024-08-21T01:35:48Z2024-08-21T01:35:48ZAtlassian Guard billing system is flagging more users as billable than it should<p><small>Aug <var data-var='date'>21</var>, <var data-var='time'>01:35</var> UTC</small><br><strong>Resolved</strong> - We have identified the root cause and have mitigated the problem. The issue has been resolved and the service is operating normally.</p><p><small>Aug <var data-var='date'>21</var>, <var data-var='time'>00:09</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Aug <var data-var='date'>21</var>, <var data-var='time'>00:04</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with Atlassian Guard billing marking as billable more users than expected that is impacting some Atlassian Guard customers. We will provide more details soon.</p>tag:guard.status.atlassian.com,2005:Incident/217064792024-08-11T04:21:06Z2024-08-11T04:21:06ZAdminHub Authentication Policies and Identity Providers sections are slow to load, or not loading at all<p><small>Aug <var data-var='date'>11</var>, <var data-var='time'>04:21</var> UTC</small><br><strong>Resolved</strong> - The issue has been resolved and the service is operating normally.</p><p><small>Aug <var data-var='date'>11</var>, <var data-var='time'>01:00</var> UTC</small><br><strong>Update</strong> - We have identified the root cause of the and have mitigated the problem. We are now monitoring closely.</p><p><small>Aug <var data-var='date'>10</var>, <var data-var='time'>23:55</var> UTC</small><br><strong>Monitoring</strong> - We've currently mitigated the issue and we're monitoring for any related errors.</p><p><small>Aug <var data-var='date'>10</var>, <var data-var='time'>22:50</var> UTC</small><br><strong>Update</strong> - We're still investigating an issue that may cause the Authentication Policies, Identity Providers sections, and the new organization creation experience in admin.atlassian.com to load slowly or fail to load.<br /><br />This is not affecting Authentication policies in place, and it's not affecting linked Identity providers either but may prevent customers from modifying/creating new Authentication Policies and creating new organizations in Atlassian Cloud.</p><p><small>Aug <var data-var='date'>10</var>, <var data-var='time'>21:46</var> UTC</small><br><strong>Investigating</strong> - We're currently investigating an issue that may cause the Authentication Policies, Identity Providers sections, and the new organization creation experience in admin.atlassian.com to load slowly or fail to load.<br /><br />This is not affecting Authentication policies in place, and it's not affecting linked Identity providers either but may prevent customers from modifying/creating new Authentication Policies and creating new organizations in Atlassian Cloud. We will provide more details once we identify the root cause.</p>tag:guard.status.atlassian.com,2005:Incident/215796502024-07-31T08:30:03Z2024-07-31T08:30:03ZDelayed Audit Log Events<p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>08:30</var> UTC</small><br><strong>Resolved</strong> - Between 30th July 20:06 UTC to 31st July 08:19 UTC, we experienced delayed processing of Audit Log events for Guard. The issue has been resolved and the service is operating normally.</p><p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>06:00</var> UTC</small><br><strong>Monitoring</strong> - We are monitoring delayed processing of audit log events impacting customers. These delayed events are in the queue for processing. Will provide an update when back to normal.</p>tag:guard.status.atlassian.com,2005:Incident/213017492024-07-04T00:50:06Z2024-07-04T00:50:06ZSome products are hard down<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>00:50</var> UTC</small><br><strong>Resolved</strong> - Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for some of the products. . The issue has been resolved and the service is operating normally.</p><p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>00:49</var> UTC</small><br><strong>Update</strong> - Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for some of the products. The issue has been resolved and the service is operating normally.</p><p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>21:45</var> UTC</small><br><strong>Monitoring</strong> - We have mitigated the problem and continue looking into the root cause.<br />The outage was between 8:08pm 03/07 UTC - 08:31pm 03/07 UTC<br />We are now monitoring closely.</p><p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>20:51</var> UTC</small><br><strong>Investigating</strong> - 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.</p>tag:guard.status.atlassian.com,2005:Incident/212412452024-06-28T05:24:21Z2024-06-28T05:24:21ZAzure Sync for nested groups is not syncing new user and group information<p><small>Jun <var data-var='date'>28</var>, <var data-var='time'>05:24</var> UTC</small><br><strong>Resolved</strong> - The issue has been resolved and the service is operating normally.</p><p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>18:25</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance for some Atlassian Guard customers. We will provide more details within the next hour.</p>tag:guard.status.atlassian.com,2005:Incident/211344912024-06-17T14:32:55Z2024-06-17T14:32:55ZUnavailability of the Last Active Timestamp status<p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>14:32</var> UTC</small><br><strong>Resolved</strong> - Between 1:39 AM UTC to 2:01 PM UTC, we experienced the unavailability of the Last Active Timestamp status in the new user experience under the Cloud organization. The issue has been resolved and the service is operating normally.</p><p><small>Jun <var data-var='date'>17</var>, <var data-var='time'>12:01</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with the unavailability of the Last Active Timestamp status in the new user experience under the Cloud organization that is impacting some of the Cloud products. We will provide more details shortly.</p>tag:guard.status.atlassian.com,2005:Incident/209858372024-06-04T00:31:09Z2024-06-17T04:39:58ZError responses across multiple Cloud products<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>00:31</var> UTC</small><br><strong>Resolved</strong> - 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.</p><p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>23:10</var> UTC</small><br><strong>Identified</strong> - 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.</p>tag:guard.status.atlassian.com,2005:Incident/206232162024-04-24T20:03:48Z2024-06-17T04:39:58ZDelayed SCIM group sync<p><small>Apr <var data-var='date'>24</var>, <var data-var='time'>20:03</var> UTC</small><br><strong>Resolved</strong> - The issue was resolved. All the groups are sync and the system is healthy. The incident is closed.</p><p><small>Apr <var data-var='date'>24</var>, <var data-var='time'>15:54</var> UTC</small><br><strong>Identified</strong> - We continue to work on resolving the delayed SCIM group sync from the provisioning directory to individual Cloud sites. We have mitigated the root cause and are seeing recovery of sync tasks.</p><p><small>Apr <var data-var='date'>24</var>, <var data-var='time'>13:33</var> UTC</small><br><strong>Investigating</strong> - We are investigating delayed SCIM group sync from the provisioning directory to individual Cloud sites.</p>tag:guard.status.atlassian.com,2005:Incident/204373412024-04-03T10:21:04Z2024-06-17T04:39:58ZAdmin Portal Feature Access Issue<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>10:21</var> UTC</small><br><strong>Resolved</strong> - Between 6:30 AM UTC to 9:50 AM UTC, we experienced failures in accessing some features from the Admin Portal. The issue has been resolved and the service is operating normally.</p><p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>09:47</var> UTC</small><br><strong>Identified</strong> - We are investigating an issue causing failures in accessing some features from the Admin Portal, which is impacting some of our Cloud customers. We have identified the root cause and anticipate recovery shortly.</p>tag:guard.status.atlassian.com,2005:Incident/201024212024-02-29T02:53:17Z2024-06-17T04:39:58ZInvestigating 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:28</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:guard.status.atlassian.com,2005:Incident/200419262024-02-22T00:22:56Z2024-06-17T04:39:58ZAudit logs fetching was failing<p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>00:22</var> UTC</small><br><strong>Resolved</strong> - Between 20:24 UTC to 20:55 UTC, we experienced outage in audit logs for Atlassian Access. 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'>21:44</var> UTC</small><br><strong>Monitoring</strong> - Audit logs was down between 12:24pm to 12:55pm PST. There was no data loss. The issue is mitigated at this time, but we are monitoring the service.</p>tag:guard.status.atlassian.com,2005:Incident/199871722024-02-14T23:32:18Z2024-06-17T04:39:58ZService 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:guard.status.atlassian.com,2005:Incident/196610372024-01-12T17:13:28Z2024-06-17T04:39:58ZDelayed 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:guard.status.atlassian.com,2005:Incident/194524802023-12-19T19:00:55Z2023-12-19T19:00:55ZAPI tokens search database upgrade<p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>19:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>18:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>22:30</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time. During the maintenance, viewing and searching User API tokens on the API tokens page may be unavailable.</p>tag:guard.status.atlassian.com,2005:Incident/194213772023-12-14T19:30:40Z2023-12-14T19:30:40ZAPI tokens search database upgrade<p><small>Dec <var data-var='date'>14</var>, <var data-var='time'>19:30</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>14</var>, <var data-var='time'>18:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>21:02</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time. During the maintenance, User API tokens may be unavailable.</p>tag:guard.status.atlassian.com,2005:Incident/193161722023-12-04T17:15:04Z2024-06-17T04:39:58ZEgress 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>tag:guard.status.atlassian.com,2005:Incident/189058222023-10-24T10:01:20Z2024-06-17T04:39:58ZEmail domain unverified<p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>10:01</var> UTC</small><br><strong>Resolved</strong> - Between 22:00 UTC 23rd October and 07:45 UTC 24th October, we experienced an issue with custom domain validation, this resulted in Atlassian Access notification emails for some customers to be sent from generic Atlassian email domains rather than the custom domain email address. The issue has been resolved and the service is operating normally.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>07:47</var> UTC</small><br><strong>Update</strong> - We have identified the issue and a fix is currently being implemented. We expect this issue to be resolved shortly.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>06:48</var> UTC</small><br><strong>Identified</strong> - We identified that the mitigation method doesn't fix the issue in some affected Cloud instances. We are continuing with the investigation.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>06:15</var> UTC</small><br><strong>Monitoring</strong> - We have mitigated the problem. We are now monitoring this closely.<br /><br />Please contact us at https://support.atlassian.com/contact/ if you are still facing issues with email domain verification.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>05:04</var> UTC</small><br><strong>Identified</strong> - We continue to work on resolving the issue with domain verification. We have identified the root cause and expect recovery shortly.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>02:44</var> UTC</small><br><strong>Update</strong> - The investigation is still ongoing. We are working on a mitigation.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>01:49</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue. We are aware that this incident is impacting custom email configuration and some Jira notifications are being sent with the default email address instead of the configured custom email.<br /><br />We will provide more details in the next hour.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>00:22</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with emails that have been sent out to admins stating domain verification is failing. We will provide more details within the next hour.</p>tag:guard.status.atlassian.com,2005:Incident/185414432023-09-19T07:23:36Z2024-06-17T04:39:58ZDegraded performance in Cloud<p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>07:23</var> UTC</small><br><strong>Resolved</strong> - Between 09/18 10:47 UTC to 09/19 04:15 UTC, we experienced degraded performance for some Confluence, Jira Work Management, Jira Service Management, Jira Software, Trello, Atlassian Access, and Jira Product Discovery customers. The issue has been resolved and the service is operating normally.</p><p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>05:45</var> UTC</small><br><strong>Update</strong> - Services are confirmed to be stable. We are performing final validation checks before confirming the incident's resolution.</p><p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>04:56</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the downgraded performance and have mitigated the problem. We are monitoring this closely.</p><p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>03:08</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance for some Atlassian Access Cloud customers. We will provide more details within the next hour.</p>tag:guard.status.atlassian.com,2005:Incident/185391662023-09-18T22:37:28Z2024-06-17T04:39:58ZDegraded performance in Cloud<p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>22:37</var> UTC</small><br><strong>Resolved</strong> - The issues with Access have been mitigated and the incident is being marked resolved for Access.</p><p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>21:04</var> UTC</small><br><strong>Monitoring</strong> - An outage with a cloud provider is impacting multiple Atlassian Cloud products including Access, Confluence, Trello, and Jira Products. We will provide more details within the next hour.</p>tag:guard.status.atlassian.com,2005:Incident/184907022023-09-13T19:32:02Z2024-06-17T04:39:58ZAtlassian Account login issues<p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>19:32</var> UTC</small><br><strong>Resolved</strong> - Between 12:45 UTC to 15:30 UTC, we experienced login and signup issues for Atlassian Accounts. The issue has been resolved and the service is operating normally.<br /><br />We will publish a post-incident review with the details of the incident and the actions we are taking to prevent similar problem in the future.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>17:36</var> UTC</small><br><strong>Update</strong> - We are no longer seeing occurrences of the Atlassian Accounts login errors, all clients should be able to successfully login now. We will continue to monitor.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>16:30</var> UTC</small><br><strong>Update</strong> - We can see a reduction in the Atlassian Accounts login issues after the mitigation actions were taken. We are still monitoring closely and will continue to provide updates.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>15:21</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the Atlassian Accounts login issues impacting Cloud Customers and have mitigated the problem. We are now monitoring this closely.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>14:08</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with Atlassian Accounts login that is impacting some Cloud customers. We will provide more details within the next hour.</p>