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

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
https://status.atlassian.com Statuspage Mon, 20 Oct 2025 18:21:14 +0000 <p><small>Apr <var data-var='date'>30</var>, <var data-var='time'>06:43</var> UTC</small><br><strong>Completed</strong> - okie dokie, RDSs have been upgraded as quickly as expected, nothing related seems to have exploded in the time since, so i think we're in the clear, yay</p><p><small>Apr <var data-var='date'>30</var>, <var data-var='time'>06:31</var> UTC</small><br><strong>Update</strong> - update: from the AWS console for commercial production:<br />- April 30, 2025, 16:09 (UTC+10:00) Multi-AZ instance failover completed<br />- April 30, 2025, 16:09 (UTC+10:00) The RDS instance was modified by customer.<br />- April 30, 2025, 16:08 (UTC+10:00) DB instance restarted<br />- April 30, 2025, 16:08 (UTC+10:00) The parameter max_wal_senders was set to a value incompatible with replication. It has been adjusted from 20 to 65.<br />- April 30, 2025, 16:08 (UTC+10:00) Multi-AZ instance failover started.<br />- April 30, 2025, 16:01 (UTC+10:00) Applying modification to database instance class<br />so it looks like that took 2 minutes from the RDS perspective, and we did see some 5XX responses from the Micros API during this time</p><p><small>Apr <var data-var='date'>30</var>, <var data-var='time'>06:04</var> UTC</small><br><strong>Update</strong> - update: we've kicked off the deployments:<br />- commercial production: https://deployment-bamboo.internal.atlassian.com/deploy/viewDeploymentResult.action?deploymentResultId=3456381285<br />- FedRAMP-moderate production: https://deployment-bamboo.internal.atlassian.com/deploy/viewDeploymentResult.action?deploymentResultId=3456381287<br />- it's hard to predict exactly when, but there should be separate 2-3 minute outages, and those should start 10-15 minutes from now</p><p><small>Apr <var data-var='date'>30</var>, <var data-var='time'>05:32</var> UTC</small><br><strong>Scheduled</strong> - - 2x separate periods of outage, each expected to be 2-3 minutes<br />- Micros API for commercial production from db.t4g.large to db.m8g.large<br />- Micros API for FedRAMP-moderate from db.t4g.large to db.m8g.large<br />- https://hello.atlassian.net/wiki/spaces/MCORE/pages/5218781089/LDR+UA-13147+AWS+deadline+versus+micros-server+RDSs<br />- https://hello.jira.atlassian.cloud/browse/MICROSCORE-4348</p> Wed, 30 Apr 2025 06:43:43 +0000 Wed, 30 Apr 2025 07:00:00 +0000 https://status.atlassian.com/incidents/mt5zzmkk76s2 https://status.atlassian.com/incidents/mt5zzmkk76s2 <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>07:31</var> UTC</small><br><strong>Resolved</strong> - We are aware of an issue that was impacting user authentication to Atlassian services between 6:10AM Tuesday 4th March UTC and 6:35AM Tuesday 4th March UTC.<br />Users that were already logged in would not have been impacted by this issue.<br />A deployment suspected of causing this issue was rolled back and the problem was subsequently resolved.</p> Tue, 04 Mar 2025 07:31:46 +0000 https://status.atlassian.com/incidents/8xc8jr91pcjh https://status.atlassian.com/incidents/8xc8jr91pcjh <p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>09:02</var> UTC</small><br><strong>Completed</strong> - Scheduled maintenance is now complete. The writes operations to Marketplace were stopped for 20 minutes. Now, all the operations are back to normal.</p><p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>06: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'>19</var>, <var data-var='time'>11:43</var> UTC</small><br><strong>Scheduled</strong> - Marketplace will be undergoing a scheduled maintenance during this time window. We will be in read-only mode during this time.</p> Sun, 22 Dec 2024 09:02:18 +0000 Sun, 22 Dec 2024 09:30:00 +0000 https://status.atlassian.com/incidents/8mv15ng7blzr https://status.atlassian.com/incidents/8mv15ng7blzr <p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>21:17</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>21:10</var> UTC</small><br><strong>Verifying</strong> - Verification is currently underway for the maintenance items.</p><p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>20:13</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'> 8</var>, <var data-var='time'>20:12</var> UTC</small><br><strong>Scheduled</strong> - Atlassian Knowledge Base (fonelucen.atlassian.com) scheduled maintenance window:<br /><br />- Starting at 8:00 PM UTC Sunday, December 8th<br />- Ending at 10:00 PM UTC Sunday, December 8th</p> Sun, 08 Dec 2024 21:17:02 +0000 Sun, 08 Dec 2024 22:13:00 +0000 https://status.atlassian.com/incidents/h0g5zv20wppp https://status.atlassian.com/incidents/h0g5zv20wppp <p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>13:15</var> UTC</small><br><strong>Resolved</strong> - We have identified the root cause of the issue with an internal infrastructure component that has been impacting the provisioning process for the Mumbai Region with several Atlassian Cloud products. All affected products are now back online and no further impact has been observed.</p><p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>18:33</var> UTC</small><br><strong>Update</strong> - We have identified the root cause of an issue with an internal infrastructure component that has been impacting the provisioning process for the Mumbai Region. <br />This issue has led to a performance impact or slowness in product provisioning. <br /><br />We are working on a fix to resolve the issue and recovery is in progress.</p><p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>10:56</var> UTC</small><br><strong>Monitoring</strong> - The slowness issue has been resolved, and we are actively monitoring the systems to ensure stability.</p><p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>09:23</var> UTC</small><br><strong>Investigating</strong> - Our team is currently investigating the issue. We are working to identify the cause and will provide updates as soon as possible.</p> Tue, 10 Sep 2024 13:15:07 +0000 https://status.atlassian.com/incidents/kl4d5mfn26kc https://status.atlassian.com/incidents/kl4d5mfn26kc <p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>12:43</var> UTC</small><br><strong>Resolved</strong> - Systems have recovered, and the issue has been mitigated. All affected products are fully operational, with no further impact observed.</p><p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>10:26</var> UTC</small><br><strong>Investigating</strong> - We are investigating issues with slow loading and long responsive time for all products (Jira, JSM, JSW and Confluence) and will provide updates here soon.</p> Tue, 10 Sep 2024 12:43:48 +0000 https://status.atlassian.com/incidents/m0nz4gbbjmz2 https://status.atlassian.com/incidents/m0nz4gbbjmz2 <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>18:12</var> UTC</small><br><strong>Resolved</strong> - Earlier today, we experienced RDS problems for Jira, Jira Service Management, and Jira Work Management. The issue has been resolved, and the services are operating normally.</p><p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>17:13</var> UTC</small><br><strong>Monitoring</strong> - We identified the root cause of the RDS problems causing issues for Jira, Jira Service Management, and Jira Work Management. We mitigated the issue and are now monitoring the fix.</p><p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>16:19</var> UTC</small><br><strong>Investigating</strong> - We are observing different RDS problems in different environments for Jira, Jira Service Management, and Jira Work Management. We are actively working on this and will provide more updates here soon.</p><p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>16:01</var> UTC</small><br><strong>Identified</strong> - We are observing different RDS problems in different environments for Jira, Jira Service Management, and Jira Work Management. We are actively working on this and will provide more updates here soon.</p><p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>10:56</var> UTC</small><br><strong>Monitoring</strong> - We’ve taken steps to address the issue by scaling up the RDS instances, and we will continue to monitor the systems to ensure everything remains stable.</p><p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>08:56</var> UTC</small><br><strong>Investigating</strong> - We are investigating issues with Latency and 5xx errors for Jira, Jira Service Management, Jira Work Management due to High RDS CPU on several EU-Central environment and will provide updates here soon.</p> Mon, 09 Sep 2024 18:12:32 +0000 https://status.atlassian.com/incidents/d8jljnw353f3 https://status.atlassian.com/incidents/d8jljnw353f3 <p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>11:15</var> UTC</small><br><strong>Resolved</strong> - The issue with scheduling App data residency migrations has been resolved and the service is operating normally.</p><p><small>Aug <var data-var='date'>20</var>, <var data-var='time'>11:46</var> UTC</small><br><strong>Investigating</strong> - Data residency migrations are currently not possible for Cloud customers. If you attempt a Data residency migration, you will encounter an error message, “We are unable to schedule your move” when you get to the “Review and submit your request” page.<br />An update will be shared here as soon as this service is resumed.</p> Fri, 23 Aug 2024 11:15:08 +0000 https://status.atlassian.com/incidents/2rsqj1hmdg82 https://status.atlassian.com/incidents/2rsqj1hmdg82 <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>03:54</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 . JIRA product impacted with issue creation and project creation. While Confluence was impacted with public link access by anonymous user and the mission control page. Confluence issue was fixed at 04-07-2024 02:30 UTC. 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> Thu, 04 Jul 2024 03:54:28 +0000 https://status.atlassian.com/incidents/2spys43jxslj https://status.atlassian.com/incidents/2spys43jxslj <p><small>Jun <var data-var='date'>25</var>, <var data-var='time'>05:30</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jun <var data-var='date'>25</var>, <var data-var='time'>03:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jun <var data-var='date'>24</var>, <var data-var='time'>04:47</var> UTC</small><br><strong>Scheduled</strong> - We are planning a scheduled maintenance during this time. It is possible that Marketplace webpages may experience downtime or reduced performance during this period.</p> Tue, 25 Jun 2024 05:30:02 +0000 Tue, 25 Jun 2024 05:30:00 +0000 https://status.atlassian.com/incidents/s04tx91jb4nb https://status.atlassian.com/incidents/s04tx91jb4nb <p><small>Jun <var data-var='date'>16</var>, <var data-var='time'>09:32</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jun <var data-var='date'>16</var>, <var data-var='time'>07:40</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jun <var data-var='date'>16</var>, <var data-var='time'>07:38</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing a scheduled maintenance in this window.</p> Sun, 16 Jun 2024 09:32:09 +0000 Sun, 16 Jun 2024 10:40:00 +0000 https://status.atlassian.com/incidents/t22c1rn6f0rg https://status.atlassian.com/incidents/t22c1rn6f0rg <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>04:30</var> UTC</small><br><strong>Resolved</strong> - Between 05 June 23:30 UTC and 06 June 04:34 UTC, we experienced issues with some of the pages on www.atlassian.com. The issue has been resolved, and the pages are operating normally.</p><p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>03:12</var> UTC</small><br><strong>Identified</strong> - We continue to work on resolving the issue with www.atlassian.com. We have identified the root cause and expect recovery shortly.</p><p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>01:30</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of intermittent errors on some Atlassian, Opsgenie, Atlassian Access, and Compass-related www.atlassian.com web pages. Once we identify the root cause, we will provide more details.</p> Thu, 06 Jun 2024 04:30:02 +0000 https://status.atlassian.com/incidents/4dh7m57xqhfq https://status.atlassian.com/incidents/4dh7m57xqhfq <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> Wed, 14 Feb 2024 23:32:18 +0000 https://status.atlassian.com/incidents/gg9z8g8xsxc7 https://status.atlassian.com/incidents/gg9z8g8xsxc7 <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> Wed, 07 Feb 2024 17:44:38 +0000 https://status.atlassian.com/incidents/5187qzxv1zvg https://status.atlassian.com/incidents/5187qzxv1zvg <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> Fri, 12 Jan 2024 17:13:28 +0000 https://status.atlassian.com/incidents/71sdcbz9gy53 https://status.atlassian.com/incidents/71sdcbz9gy53 <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> Tue, 19 Dec 2023 03:28:15 +0000 https://status.atlassian.com/incidents/lvq7pq0zbgvr https://status.atlassian.com/incidents/lvq7pq0zbgvr <p><small>Nov <var data-var='date'>22</var>, <var data-var='time'>04:27</var> UTC</small><br><strong>Resolved</strong> - Between 01:18 AM UTC to 03:31 AM UTC, we encountered a problem where some organisation admins were not able to access User Management on the Admin hub. We have identified the root cause of this issue and fixed it. Admin hub is functioning as expected now.</p> Wed, 22 Nov 2023 04:27:42 +0000 https://status.atlassian.com/incidents/httczs7wslz8 https://status.atlassian.com/incidents/httczs7wslz8 <p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>10:00</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 Jira Software, Jira Work Management, Jira Service management, 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:49</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:14</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:43</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> Tue, 24 Oct 2023 10:00:52 +0000 https://status.atlassian.com/incidents/3sf6vg9v8nqm https://status.atlassian.com/incidents/3sf6vg9v8nqm <p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>17:20</var> UTC</small><br><strong>Resolved</strong> - 100% resolved and services running normally</p><p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>17:01</var> UTC</small><br><strong>Update</strong> - 99% of issues fixed and services are back to normal. Last 1% are manually begin fixed</p><p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>16:20</var> UTC</small><br><strong>Update</strong> - We've solved 52% of the issues and are still on track to recover 100% within the original timeframe</p><p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>15:47</var> UTC</small><br><strong>Monitoring</strong> - We've solved 15% of the issues and have a plan to recover 100% exponentially within the hour</p><p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>15:01</var> UTC</small><br><strong>Update</strong> - We started fixing the affected tenants, we will post an update on the estimated time to resolve all tenants in the next hour</p><p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>14:28</var> UTC</small><br><strong>Identified</strong> - We identified an issue with the product provisioning service. We identified the issue and we are working on a fix. <br />We will post an update in the next hour with estimated fix time</p> Wed, 04 Oct 2023 17:20:32 +0000 https://status.atlassian.com/incidents/b2lqb2yxry16 https://status.atlassian.com/incidents/b2lqb2yxry16 <p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>20:27</var> UTC</small><br><strong>Resolved</strong> - Between 04:36 UTC to 17:50 UTC, we experienced intermittent issues on Atlassian.com and Bitbucket Marketing pages. The issue has been resolved and the service is operating normally.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>18:42</var> UTC</small><br><strong>Update</strong> - We are still investigating intermittent issues with these two domains. We will provide more details within the next hour.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>17:44</var> UTC</small><br><strong>Update</strong> - We are still investigating intermittent issues with these two domains. We will provide more details within the next hour.</p><p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>16:26</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance for Atlassian Cloud customers. We will provide more details within the next hour.</p> Fri, 29 Sep 2023 20:27:18 +0000 https://status.atlassian.com/incidents/lgl84rzhxd0d https://status.atlassian.com/incidents/lgl84rzhxd0d <p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>05:19</var> UTC</small><br><strong>Resolved</strong> - Between 04:00 UTC to 05:00 UTC, we experienced a partial outage for Bitbucket Pipelines, issues viewing in-product attachments; and degraded performance across all products. The issue has been resolved and all services are operating normally.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>04:47</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause, initiated mitigation actions, and are seeing a reduction in errors when scaling up in response to customer traffic. We are still monitoring closely and will continue to provide updates.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>04:12</var> UTC</small><br><strong>Update</strong> - A major infrastructure outage is affecting our ability to scale up in response to customer traffic. We are pre-emptively disabling any downscaling to minimize future impact. This is primarily affecting Bitbucket Pipelines, and attachment storage for all products. All regions are affected. We will provide more details in the next hour.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>04:02</var> UTC</small><br><strong>Identified</strong> - A major infrastructure outage is affecting our ability to scale up in response to customer traffic. We are pre-emptively disabling any downscaling to minimize future impact. This is primarily affecting Bitbucket Pipelines, and attachment storage for all products. All regions are affected. We will provide more details in the next hour.</p> Fri, 15 Sep 2023 05:19:25 +0000 https://status.atlassian.com/incidents/4jkh49j0jjh6 https://status.atlassian.com/incidents/4jkh49j0jjh6 <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>15:59</var> UTC</small><br><strong>Resolved</strong> - We mitigated the issue with Sign-ups, Product Activation, and Billing, and the systems are back to BAU, and all functionality is restored.</p><p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>14:25</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the Sign-ups, Product Activation, and Billing not working and have mitigated the problem. We are now monitoring closely.</p> Wed, 02 Aug 2023 15:59:20 +0000 https://status.atlassian.com/incidents/vk4mksp2hvj8 https://status.atlassian.com/incidents/vk4mksp2hvj8 <p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>15:37</var> UTC</small><br><strong>Resolved</strong> - We experienced performance issues and outages for several Atlassian Cloud Products. The issue has been resolved and the service is operating normally.</p><p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>13:17</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of an issue with an internal infrastructure component that has been impacting multiple Cloud products, including Jira Software, Jira Service Management and Confluence, and customers. This issue had lead to a performance impact and, in some cases, outages.<br /><br />We have implemented a fix to resolve the issue and recovery is in progress.</p><p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>11:18</var> UTC</small><br><strong>Identified</strong> - We are investigating an issue with an internal infrastructure component that is impacting multiple Cloud products, including Jira Software, Bitbucket, Jira Service Management and Confluence, and customers. These issues include performance impact and, in some cases, outages.<br /><br />Users may experience slow loading and uploading of attachments, login issues or inability for new customers to sign up. We have identified the root cause and are actively working on the service recovery.</p> Thu, 06 Jul 2023 15:37:19 +0000 https://status.atlassian.com/incidents/pzh5b8cvfk2g https://status.atlassian.com/incidents/pzh5b8cvfk2g <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>06:41</var> UTC</small><br><strong>Resolved</strong> - Between 05:15 UTC to 05:55 UTC, we experienced user registration failing. The issue has been resolved and the service is operating normally.</p> Fri, 05 Aug 2022 06:41:46 +0000 https://status.atlassian.com/incidents/fthwx4svyskf https://status.atlassian.com/incidents/fthwx4svyskf <p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>03:33</var> UTC</small><br><strong>Resolved</strong> - Between 2:05 UTC and 2:42 UTC, we experienced failures to load some marketplace apps for customers tenanted in the apse, eu-west and eu-central regions. The issue has been resolved and the service is operating normally.</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>03:17</var> UTC</small><br><strong>Monitoring</strong> - We are investigating reports of intermittent errors for some marketplace apps across the following regions: apse, eu west and eu central. Service has now been restored to each of the affected regions. We are continuing to monitor, but believe there is no further impact to customers and Atlassian developers.</p> Wed, 22 Jun 2022 03:33:33 +0000 https://status.atlassian.com/incidents/wpphfps5ffpj https://status.atlassian.com/incidents/wpphfps5ffpj