Atlassian Guard

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-14 05:11 UTC

   Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

2. identified 2026-05-14 05:24 UTC

   It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team...

3. identified 2026-05-14 05:34 UTC

   Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update...

4. monitoring 2026-05-14 05:43 UTC

   Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken...

5. monitoring 2026-05-14 06:39 UTC

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been...

6. monitoring 2026-05-14 06:40 UTC

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been...

7. resolved 2026-05-14 06:48 UTC

   All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

8. postmortem 2026-05-19 19:08 UTC

   ### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 01:31 UTC

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. identified 2026-05-08 02:15 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

3. identified 2026-05-08 03:00 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

4. identified 2026-05-08 03:00 UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

5. identified 2026-05-08 04:10 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

6. identified 2026-05-08 04:10 UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

7. identified 2026-05-08 04:10 UTC

   We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each...

8. monitoring 2026-05-08 05:53 UTC

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation...

9. monitoring 2026-05-08 08:03 UTC

   We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

10. monitoring 2026-05-08 11:12 UTC

    Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We...

11. resolved 2026-05-08 19:45 UTC

    On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

12. postmortem 2026-05-20 06:55 UTC

    All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-04-13 07:29 UTC

   Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact. Our team is investigating with urgency, and we...

2. monitoring 2026-04-13 08:33 UTC

   Atlassian account login services are now operating as expected, and we are not observing new errors. We continue to closely monitor our systems to ensure they remain stable. We will provide another update within 60 minutes or sooner if we detect a change in status.

3. resolved 2026-04-13 10:17 UTC

   On April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC, some users were unable to log in to Atlassian products with their Atlassian accounts. The underlying issue has been addressed, and authentication services have remained stable with no new impact observed.

4. postmortem 2026-04-21 02:35 UTC

   ### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-08 06:01 UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

2. investigating 2026-04-08 06:01 UTC

   The impact of this incident is now understood to also be impacting search in Jira and Confluence, as well as additional downstream impacts to Rovo Chat, User Management, Administration and Guard. Our team is continuing to investigate with urgency and we will provide further...

3. investigating 2026-04-08 06:24 UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

4. investigating 2026-04-08 06:25 UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

5. identified 2026-04-08 06:25 UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...

6. identified 2026-04-08 07:40 UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...

7. identified 2026-04-08 07:40 UTC

   Confluence and Jira search reliability is improving, and we expect full recovery shortly; we will continue to closely monitor the services to ensure they remain stable.

8. identified 2026-04-08 08:33 UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...

9. identified 2026-04-08 08:33 UTC

   We have restored core search functionality and services are operating again, but some customers may still experience delays when searching for data changed within the last hour while new data continues to be indexed. We are actively working to complete reindexing and will update...

10. identified 2026-04-08 09:03 UTC

    We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...

11. monitoring 2026-04-08 09:03 UTC

    The issue has been resolved, and services are now operating normally. Some customers may still experience delays when searching for data changed within the last hour, while new data continues to be indexed. We'll continue to monitor closely to confirm stability.

12. resolved 2026-04-08 11:43 UTC

    The issue has now been resolved, and the service is operating normally for all affected customers.

13. postmortem 2026-04-17 16:24 UTC

    ### Summary On April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-02-18 11:28 UTC

   We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

2. resolved 2026-02-18 11:30 UTC

   We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Signup

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-12-27 04:42 UTC

   We have taken steps to mitigate the issue and are seeing recovery in the affected services. Our teams will continue to closely monitor the situation and are actively working to confirm that all services are fully restored. We will provide further updates as we make additional...

2. resolved 2025-12-27 05:20 UTC

   We have successfully mitigated the incident and all affected services are now fully operational. Our teams have verified that normal functionality has been restored across all areas. Thank you for your patience and understanding while we worked to resolve this issue.

3. postmortem 2026-01-30 04:11 UTC

   ### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available. The issue was triggered when **TLS...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-15 20:23 UTC

   We are actively investigating reports of a partial service disruption affecting Atlassian Guard. We'll share updates here as more information is available.

2. investigating 2025-12-15 20:38 UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. We'll continue to share additional updates here in 60 minutes or as more information becomes available.

3. identified 2025-12-15 21:42 UTC

   Our teams are continuing work on mitigations. We'll continue to share additional updates here in 60 minutes or as more information becomes available. Note: Any previously failed Guard provisioning and open workflows have been replayed by Atlassian. No actions are needed from...

4. resolved 2025-12-15 22:07 UTC

   On December 15th, 2025, affected Guard users in US Prod East region may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers. Note: All previously failed Guard provisioning and open workflows...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-15 16:16 UTC

   We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo. We'll share updates here as more information is available.

2. identified 2025-12-15 16:26 UTC

   We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, and Rovo. We'll share updates here as more information is available.

3. identified 2025-12-15 16:48 UTC

   We have identified the cause of the issue, and our teams are diligently working on mitigations. We're currently seeing signs of improvements. We'll continue to share additional updates here in 60 minutes or as more information becomes available.

4. identified 2025-12-15 17:47 UTC

   Our teams are continuing to implement mitigations. Error rates have decreased across all products and we are seeing improvements. We will continue to provide updates here in 60 minutes or as more information becomes available.

5. resolved 2025-12-15 19:02 UTC

   On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps....

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-13 18:56 UTC

   We are investigating reports that some customers using Guard are experiencing delays or non-receipt of one-time passwords (OTP), two-factor authentication (2FA), and password reset emails. Our investigations indicate that these emails are being delivered successfully, but are...

2. monitoring 2025-11-14 04:57 UTC

   Our investigation has indicated that the issues with email delivery are related to quarantine rules in effect within our customers email service providers. For customers that are continuing to experience this issue, we encourage you to reach out to your organizations email...

3. resolved 2025-11-17 00:11 UTC

   Impacted customers have now confirmed that they are receiving their emails as expected. If you do continue to see these emails being missing or delayed, please check in with your organizations email admin to review and release them.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:56 UTC

   We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same. We shall keep you informed of the progress every hour.

2. investigating 2025-10-20 08:24 UTC

   Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same. We shall keep you informed of the progress every hour.

3. investigating 2025-10-20 09:23 UTC

   We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not...

4. investigating 2025-10-20 09:24 UTC

   We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not...

5. identified 2025-10-20 09:58 UTC

   We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

6. identified 2025-10-20 11:06 UTC

   We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

7. identified 2025-10-20 12:06 UTC

   Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

8. identified 2025-10-20 13:07 UTC

   Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

9. identified 2025-10-20 13:56 UTC

   Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

10. identified 2025-10-20 13:58 UTC

    Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

11. identified 2025-10-20 14:03 UTC

    We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide...

12. identified 2025-10-20 15:20 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

13. identified 2025-10-20 15:21 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

14. identified 2025-10-20 16:35 UTC

    Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and...

15. identified 2025-10-20 16:36 UTC

    Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and...

16. identified 2025-10-20 17:27 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

17. identified 2025-10-20 17:43 UTC

    We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and...

18. identified 2025-10-20 17:43 UTC

    We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and...

19. monitoring 2025-10-20 18:38 UTC

    There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available. We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS....

20. monitoring 2025-10-20 21:26 UTC

    Monitoring - We've started seeing continued product experience improvement. While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and...

21. monitoring 2025-10-20 22:58 UTC

    Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.

22. monitoring 2025-10-21 00:03 UTC

    Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored. The Atlassian Support portal is currently still displaying a message...

23. monitoring 2025-10-21 01:07 UTC

    We continue to see recovery progressing across all impacted products as backlogged items continue to be processed. The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is...

24. monitoring 2025-10-21 03:24 UTC

    The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues. With regards to other Atlassian products, we continue...

25. resolved 2025-10-21 05:24 UTC

    Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the...

26. postmortem 2025-10-24 17:49 UTC

    ### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-22 05:59 UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that...

2. monitoring 2025-09-22 06:55 UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

3. resolved 2025-09-22 07:17 UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

4. postmortem 2025-10-01 06:23 UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: User Provisioning

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-04 23:44 UTC

   Our team is aware of issues with users not currently receiving product invitation emails as expected. We are investigating with urgency and will provide an update as soon as possible. Please note that invitations within the product are still successful, only the email...

2. resolved 2025-08-05 04:19 UTC

   Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations. The change that caused these emails to stop being sent has been rolled back. New invitation emails should now be sent correctly for all products. For users...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Account Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-25 09:38 UTC

   We are investigating reports of errors loading Users and Groups pages in Atlassian Administration, and errors affecting user IDP syncing. We will provide more details once we identify the root cause.

2. identified 2025-06-25 10:21 UTC

   We continue to work on resolving the user syncing functionality for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. We have identified the root cause and expect recovery shortly.

3. resolved 2025-06-25 10:57 UTC

   Between 07:40 UTC and 10:31 UTC, we experienced issues affecting user syncing in Atassian Administration. This affected Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-04 17:17 UTC

   We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and...

2. resolved 2025-06-04 20:59 UTC

   Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, Data Classification, SAML-based SSO, Data Security Policies, User Provisioning, Guard Detect, Account Management, Audit Logs, Signup, API tokens

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-26 05:19 UTC

   We are aware of issues relating to authentication resulting in 503 gateway error messages. Our team is investigating with urgency and will provide an update when available.

2. monitoring 2025-05-26 05:57 UTC

   A fix for the issue causing authentication errors across multiple apps has been rolled out. We will provide further update when can confirm the issue has been fully resolved.

3. resolved 2025-05-26 06:27 UTC

   Monitoring has indicated that users are no longer receiving the error messages caused by this issue and it should now be fully resolved.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Account Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-14 00:40 UTC

   We are currently investigating this issue.

2. resolved 2025-04-14 01:33 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Account Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-01 04:37 UTC

   We are investigating reports of intermittent errors when logging into the Atlassian admin hub at https://admin.atlassian.com. Once we identify the root cause, we will provide more details.

2. identified 2024-11-01 05:01 UTC

   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.

3. monitoring 2024-11-01 05:03 UTC

   We have identified the root cause of the Atlassian Admin hub not responding and have mitigated the problem. We are now monitoring closely.

4. resolved 2024-11-01 05:22 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: User Provisioning, Account Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-25 11:37 UTC

   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. Guard Cloud customers are affected by this...

2. monitoring 2024-10-25 12:20 UTC

   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. We have taken...

3. investigating 2024-10-25 13:39 UTC

   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...

4. investigating 2024-10-25 14:37 UTC

   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...

5. investigating 2024-10-25 16:16 UTC

   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...

6. resolved 2024-10-25 17:23 UTC

   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...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-10-18 14:09 UTC

   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.

2. resolved 2024-10-18 17:38 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-08-26 05:29 UTC

   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.

2. monitoring 2024-08-26 05:33 UTC

   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. As a workaround, you may need to perform a new User or Group change.

3. resolved 2024-08-26 11:02 UTC

   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...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Account Management

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-08-21 00:04 UTC

   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.

2. investigating 2024-08-21 00:09 UTC

   We are continuing to investigate this issue.

3. resolved 2024-08-21 01:35 UTC

   We have identified the root cause and have mitigated the problem. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-10 21:46 UTC

   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. This is not affecting Authentication policies in place, and it's...

2. investigating 2024-08-10 22:50 UTC

   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. This is not affecting Authentication policies in place, and it's not...

3. monitoring 2024-08-10 23:55 UTC

   We've currently mitigated the issue and we're monitoring for any related errors.

4. monitoring 2024-08-11 01:00 UTC

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

5. resolved 2024-08-11 04:21 UTC

   The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Audit Logs

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2024-07-31 06:00 UTC

   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.

2. resolved 2024-07-31 08:30 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-03 20:51 UTC

   We are investigating an issue with that is impacting 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...

2. monitoring 2024-07-03 21:45 UTC

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

3. monitoring 2024-07-04 00:49 UTC

   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.

4. resolved 2024-07-04 00:50 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: User Provisioning

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2024-06-27 18:25 UTC

   We are investigating cases of degraded performance for some Atlassian Guard customers. We will provide more details within the next hour.

2. resolved 2024-06-28 05:24 UTC

   The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Account Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-06-17 12:01 UTC

   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.

2. resolved 2024-06-17 14:32 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-06-03 23:10 UTC

   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.

2. resolved 2024-06-04 00:31 UTC

   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.

3. postmortem 2024-06-11 00:58 UTC

   ### Summary On June 3rd, between 09:43pm and 10:58 pm UTC, Atlassian customers using multiple product\(s\) were unable to access their services. The event was triggered by a change to the infrastructure API Gateway, which is responsible for routing the traffic to the correct...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: User Provisioning

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-24 13:33 UTC

   We are investigating delayed SCIM group sync from the provisioning directory to individual Cloud sites.

2. identified 2024-04-24 15:54 UTC

   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.

3. resolved 2024-04-24 20:03 UTC

   The issue was resolved. All the groups are sync and the system is healthy. The incident is closed.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-04-03 09:47 UTC

   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.

2. resolved 2024-04-03 10:21 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Signup

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-29 01:28 UTC

   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...

2. resolved 2024-02-29 02:53 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Audit Logs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2024-02-21 21:44 UTC

   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.

2. resolved 2024-02-22 00:22 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, SAML-based SSO, User Provisioning, Account Management, Audit Logs, Signup, API tokens

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-02-14 21:57 UTC

   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.

2. identified 2024-02-14 22:31 UTC

   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.

3. monitoring 2024-02-14 22:55 UTC

   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.

4. resolved 2024-02-14 23:32 UTC

   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...

5. postmortem 2024-02-27 05:41 UTC

   ### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: User Provisioning

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-01-09 22:03 UTC

   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. We will provide more details shortly.

2. monitoring 2024-01-10 03:17 UTC

   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.

3. monitoring 2024-01-10 19:56 UTC

   The bottleneck in the Group synchronization process for SCIM Provisioning is still under work. We are closely monitoring the service.

4. monitoring 2024-01-11 18:54 UTC

   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.

5. monitoring 2024-01-11 22:36 UTC

   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.

6. monitoring 2024-01-12 06:55 UTC

   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.

7. resolved 2024-01-12 17:13 UTC

   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.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2023-12-04 16:33 UTC

   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.

2. identified 2023-12-04 16:43 UTC

   Including Atlassian Developer

3. identified 2023-12-04 16:54 UTC

   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...

4. monitoring 2023-12-04 16:59 UTC

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

5. resolved 2023-12-04 17:15 UTC

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

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-10-24 00:22 UTC

   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.

2. investigating 2023-10-24 01:49 UTC

   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. We will provide more details in the next hour.

3. investigating 2023-10-24 02:44 UTC

   The investigation is still ongoing. We are working on a mitigation.

4. identified 2023-10-24 05:04 UTC

   We continue to work on resolving the issue with domain verification. We have identified the root cause and expect recovery shortly.

5. monitoring 2023-10-24 06:15 UTC

   We have mitigated the problem. We are now monitoring this closely. Please contact us at https://support.atlassian.com/contact/ if you are still facing issues with email domain verification.

6. identified 2023-10-24 06:48 UTC

   We identified that the mitigation method doesn't fix the issue in some affected Cloud instances. We are continuing with the investigation.

7. identified 2023-10-24 07:47 UTC

   We have identified the issue and a fix is currently being implemented. We expect this issue to be resolved shortly.

8. resolved 2023-10-24 10:01 UTC

   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....

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, SAML-based SSO, User Provisioning, Account Management, Audit Logs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-09-19 03:08 UTC

   We are investigating cases of degraded performance for some Atlassian Access Cloud customers. We will provide more details within the next hour.

2. monitoring 2023-09-19 04:56 UTC

   We have identified the root cause of the downgraded performance and have mitigated the problem. We are monitoring this closely.

3. monitoring 2023-09-19 05:45 UTC

   Services are confirmed to be stable. We are performing final validation checks before confirming the incident's resolution.

4. resolved 2023-09-19 07:23 UTC

   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...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Domain Claims, SAML-based SSO, User Provisioning, Account Management, Audit Logs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2023-09-18 21:04 UTC

   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.

2. resolved 2023-09-18 22:37 UTC

   The issues with Access have been mitigated and the incident is being marked resolved for Access.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Signup

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-09-13 14:08 UTC

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

2. monitoring 2023-09-13 15:21 UTC

   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.

3. monitoring 2023-09-13 16:30 UTC

   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.

4. monitoring 2023-09-13 17:36 UTC

   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.

5. resolved 2023-09-13 19:32 UTC

   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. We will publish a post-incident review with the details of the incident and the actions we are taking to prevent...

6. postmortem 2023-09-22 00:45 UTC

   ### **SUMMARY** On Sep 13, 2023, between 12:00 PM UTC and 03: 30 PM UTC, some Atlassian users were unable to sign in to their accounts and use multiple Atlassian cloud products. The event was triggered by a misconfiguration of rate limits in an internal service which caused a...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: SAML-based SSO

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-09-12 01:34 UTC

   We have identified an issue where the Service provider entity URL and the Service provider assertion consumer service URL are not visible in the SAML SSO configuration wizard. We have identified the root cause and are now working to fix it.

2. monitoring 2023-09-12 01:36 UTC

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

3. resolved 2023-09-12 02:22 UTC

   This incident has been resolved. Service provider entity URL and the Service provider assertion consumer service URL are displayed correctly now.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-08-22 01:08 UTC

   We have resolved a case of degraded performance for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details within the...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: User Provisioning

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2023-08-15 10:46 UTC

   We're addressing an issue causing sporadic removal of synced groups from Cloud sites in Google Workspace. This is affecting permissions and access to projects. Our team is working to restore settings and prevent further occurrences. This is a recurrence of the issue reported on...

2. identified 2023-08-15 10:47 UTC

   Update: highlighting affected components

3. monitoring 2023-08-15 12:59 UTC

   Confluence and Jira customers should no longer face any issues in accessing their Atlassian Sites. We are actively investigating the root cause of the problem to provide a permanent fix.

4. monitoring 2023-08-15 13:01 UTC

   Updating affected components

5. monitoring 2023-08-15 17:57 UTC

   We identified a reoccurrence with Google Workspace sporadically removing groups from instances. This affects permissions and access to product instances. Our team is working to restore Google's incorrectly deleted settings and prevent further occurrences. In case you are...

6. monitoring 2023-08-16 11:31 UTC

   We are still investigating the recurring issue where Google Workspace is intermittently deleting groups from Atlassian Sites. This incident impacts the permissions and access to products. Our team is actively engaged in determining the cause of these erroneous deletions by...

7. monitoring 2023-08-17 08:44 UTC

   We have identified the root cause of the group deletions and have mitigated the problem. We are now monitoring closely. If this believe the issue has not been resolved for you, please don't hesitate to get in touch with Atlassian Support at https://support.atlassian.com/contact/

8. resolved 2023-08-17 21:15 UTC

   Google pushed updates for their Admin API that should resolve the group provisioning scope bad state. Any paused sync can be resumed, to restore functionality.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: User Provisioning

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-08-10 15:22 UTC

   We are investigating intermittent reports of synced groups for Google Workspace being removed and re-added without the proper permissions for their Cloud Products. We will provide more details once we identify the root cause.

2. identified 2023-08-10 16:54 UTC

   We continue to work on resolving the loss of permissions for synced groups from Google Workspace. We have identified the root cause and expect recovery shortly.

3. identified 2023-08-10 20:11 UTC

   We are still waiting for an ETA from Google to permanently resolve the issue. In the mean time we will be proactively disabling Google sync and restoring the missing permissions for synced groups for all affected sites.

4. resolved 2023-08-10 22:01 UTC

   We are no longer observing any internal logs with the issue for the past 2 hours. We don't have an official confirmation from Google, however based on our observations we are now considering this issue resolved.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-02 13:41 UTC

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

2. monitoring 2023-08-02 14:25 UTC

   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.

3. resolved 2023-08-02 15:59 UTC

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

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: A code release introduced the failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-07-06 11:18 UTC

   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....

2. monitoring 2023-07-06 13:17 UTC

   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...

3. resolved 2023-07-06 15:37 UTC

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

4. postmortem 2023-07-14 04:58 UTC

   ### **SUMMARY** We understand the importance of providing reliable and consistent service to our valued customers. On July 6, 2023, from 03:52 to 15:11 UTC, we experienced an issue with an upgraded version of a third-party tool that functions as our internal artifact management...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-07-06 08:38 UTC

   We are investigating reports of intermittent errors during login for some customers using Confluence, Jira Work Management, Jira Service Management, Jira Software, Trello, Atlassian Bitbucket, Atlassian Access, and Jira Product Discovery Cloud customers. We will provide more...

2. investigating 2023-07-06 09:03 UTC

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

3. investigating 2023-07-06 09:34 UTC

   We are investigating reports of errors during login for some customers that is impacting some Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, and...

4. investigating 2023-07-06 09:39 UTC

   We are investigating reports of errors during login for some customers that is impacting some Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, and...

5. identified 2023-07-06 10:59 UTC

   We are investigating reports of errors during login that is impacting some Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, Compass, and Atlassian...

6. monitoring 2023-07-06 12:56 UTC

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

7. resolved 2023-07-06 13:32 UTC

   Between 07:31 UTC to 12:32 UTC, we experienced errors during login for Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Product Discovery, Compass, and Atlassian Analytics....

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Account Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2023-06-13 12:04 UTC

   We are investigating an issue with our servers that is impacting some of our customers ability to perform: > New product activations; > User import; > User management. We will provide more details within the next hour.

2. identified 2023-06-13 12:46 UTC

   We are investigating an issue with our servers that is impacting some of our customers ability to perform: > New product activations; > User import; > User management. We will provide more details within the next hour.

3. monitoring 2023-06-13 13:19 UTC

   We have identified the root cause of the product actions and user management issues. The problem was now mitigated. We are now monitoring closely.

4. monitoring 2023-06-13 16:22 UTC

   We are seeing some reoccurrence of the issue and have taken some mitigation actions. We are closely monitoring the issue while those actions take effect.

5. resolved 2023-06-13 22:27 UTC

   Between 09:00 UTC to 18:00 UTC, we experienced an issue for user management and user imports for Confluence, Jira, Jira Service Management, and Jira Work Management, and Jira Product Discovery. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Signup

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-04-27 15:49 UTC

   We are investigating an issue with licensing subscription activation and reactivation that is impacting some Atlassian Access Cloud customers. We will provide more details within the next hour.

2. identified 2023-04-27 16:57 UTC

   We continue to work on resolving the issue with licensing subscription/resubscription that is impacting some Atlassian Access Cloud customers. We have identified the root cause and applied the fix for some affected customers. Expect recovery shortly.

3. identified 2023-04-27 20:10 UTC

   We're still working on the issue with licensing subscription/resubscription that is impacting some Atlassian Access Cloud customers. As mentioned, we have identified the root cause and applied the fix for some affected customers.

4. resolved 2023-04-28 15:07 UTC

   Between 20/Apr/23 12:00 AM UTC to 28/Apr/23 6:00 PM UTC, we experienced a failure with the product subscription activation and reactivation functionality for Atlassian Access. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Signup

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-02-27 09:36 UTC

   We are investigating reports of intermittent errors for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Atlassian Access, Atlas, and Compass Cloud customers. We will provide more details once we identify the root cause.

2. resolved 2023-02-27 09:52 UTC

   Between 08:20 UTC to 09:30 UTC, we experienced degraded performance on new account signups for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Atlassian Access, Atlas, and Compass. The issue has been resolved and the service is...

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: User Provisioning

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2022-12-19 04:38 UTC

   We are currently investigating errors when deactivating managed accounts for Atlassian Access customers. We will provide more details once we identify the root cause

2. investigating 2022-12-19 05:52 UTC

   We have identified an issue which is impacting Billing and Provisioning. We will provide more details once we identify the root cause.

3. resolved 2022-12-19 07:55 UTC

   Between 3:35 to 7:10 UTC, we experienced a Billing and Provisioning issue for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, and Atlassian Access. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.

Affected: Account Management, Signup

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2022-05-26 11:06 UTC

   We are investigating an issue with Atlassian Access that is impacting access to admin.atlassian.com through the browser. We will provide more details within the next hour.

2. investigating 2022-05-26 11:32 UTC

   We are gradually seeing sites recovering with access to admin.atlassian.com through the browser . We're continuing to monitor the service and deploy the fix.

3. resolved 2022-05-26 12:54 UTC

   Between 09:52 AM UTC to 12:47 PM UTC, we experienced issue impacting access to admin.atlassian.com through the browser. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Atlassian Guard's status page.