Atlassian Statuspage

Affected: HTTP Pages, Admin User+Pass, Web Portal, Statuspage, Pingdom Email, Email, Pingdom Integration, Ticketing, HTTPS Pages, Admin Google Auth, Authenticated API, External, New Relic Email, Slack, SMS, Knowledge Base, Status Embed Widget, Admin SAML 2.0, DNS Validation, Generic Email, Webhook, New Relic Integration, API Documentation, SSL Provisioning, Public API, Page Access Users, PagerDuty Webhook, Twitter, Datadog Integration, Metastatuspage, Page Google Auth, Billing, Custom Integration, Shortlinks, Jira Software Integration, Marketing Site (www.statuspage.io), Page SAML 2.0, SMS Subscription, Page IP Restriction, Signup, AWS cloudfront, AWS rds-us-west-2, AWS route53

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 2026-04-09 07:10 UTC

   Customers might intermittently experience issues when accessing Statuspage capabilities.

2. investigating 2026-04-09 07:35 UTC

   Issue has been resolved.

3. resolved 2026-04-09 07:38 UTC

   StatusPage is operational and issue has been resolved.

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

Affected: Pingdom Integration, New Relic Integration, Datadog Integration, Custom Integration

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 2026-03-19 22:52 UTC

   We are investigating a processing delay affecting system metrics. We are working on a fix and will update you shortly.

2. monitoring 2026-03-20 13:39 UTC

   The latency-reduction fix for system metrics has been deployed, and we are actively monitoring its performance.

3. monitoring 2026-03-27 07:08 UTC

   The latency fix is confirmed stable across all integrations, and we are closing this issue as resolved.

4. resolved 2026-03-27 07:08 UTC

   The latency fix is confirmed stable across all integrations, and we are closing this issue as resolved.

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

Affected: Pingdom Integration, New Relic Integration, Datadog Integration, Custom Integration

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 2026-02-26 06:18 UTC

   We are currently investigating an issue affecting the display of system metrics on statuspages.

2. identified 2026-02-26 14:11 UTC

   System Metrics fix has been rolled out to majority of the customers. We will continue a gradual rollout to other customers and monitor progress closely.

3. monitoring 2026-02-27 07:50 UTC

   System metrics has been fixed for all customers.

4. resolved 2026-03-13 18:27 UTC

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

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

Affected: HTTP Pages, Web Portal, HTTPS Pages, Status Embed Widget, Public API, Shortlinks, SMS Subscription

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 2026-02-10 21:48 UTC

   We are actively investigating reports of an intermittent partial service disruption affecting Statuspage. We'll share updates here as more information is available.

2. monitoring 2026-02-10 22:37 UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.

3. resolved 2026-02-10 23:02 UTC

   On February 10, 2026, affected Statuspage users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

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

Affected: Pingdom Integration, New Relic Integration, Datadog Integration, Custom Integration

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 2026-02-02 21:22 UTC

   We are currently investigating an issue affecting the display of system metrics on statuspages.

2. identified 2026-02-03 02:43 UTC

   Our team has identified an issue relating to the underlying data used to populate our System Metrics charts, which could cause display errors to appear on customer Statuspages. We are investigating possible solutions, and in the meantime, the System Metrics functionality within...

3. identified 2026-02-05 07:46 UTC

   Statuspage is operating normally except for the System metrics feature, which is disabled for the time being to minimize the impact to users viewing Statuspages. Customers can continue to post publicly about the status of their own systems for overall health and availability. We...

4. identified 2026-02-09 11:41 UTC

   We continue to explore possible solutions. Statuspage is operating normally except for the System metrics feature, which is disabled for the time being to minimize the impact to users viewing Statuspages. Customers can continue to post publicly about the status of their own...

5. identified 2026-02-11 12:48 UTC

   System Metrics with the new implementation is being rolled out gradually to customers, and we are closely monitoring the progress. The next update will be provided within 48 hours or sooner.

6. identified 2026-02-13 12:40 UTC

   The new System Metrics implementation has been rolled out to some customers and is performing well. We will continue a gradual rollout to other customers and monitor progress closely. The next update will be provided early next week.

7. identified 2026-02-17 14:50 UTC

   Rolling out of the new System Metrics implementation is slowed down to ensure it performs well for the rolled out customers. We continue to monitor progress and plan gradual rollout to other customers. The next update will be on Friday, Feb 20, 2026 or sooner if we achieve...

8. monitoring 2026-02-20 11:26 UTC

   New System Metrics has been rolled out to the majority of our customers, and we are actively monitoring its performance. As Librato has deprecated their platform, we are in the process of removing the Librato integration from our product. Our next update is planned for Monday,...

9. resolved 2026-02-23 10:00 UTC

   New System metrics implementation has been successfully enabled for all customers.

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

Affected: Authenticated API

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

1. identified 2026-02-02 10:56 UTC

   Customers may be experiencing issues accessing Statuspage via the API due to the deprecation of existing keys. Our team is actively working on the fix and will provide an update soon. In the meantime, as a workaround, please generate new credentials with a Statuspage API key and...

2. monitoring 2026-02-02 15:47 UTC

   We have started rolling out a fix and are currently monitoring its impact. We’ll share an update as soon as the issue has been fully resolved.

3. resolved 2026-02-02 16:40 UTC

   The incident has been resolved.

4. postmortem 2026-03-11 03:53 UTC

   On 2 February 2026 between 08:52 and 16:40 UTC, some Statuspage customers’ API-based integrations started failing with authorization errors when a planned cleanup of old API keys unintentionally disabled new keys as well. Statuspage UI and core product functions remained...

Excerpts are shortened. Read the full incident on Atlassian Statuspage'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. resolved 2025-10-29 10:00 UTC

   On October 29th, between 9:50 UTC and 10:04 UTC, some Statuspage customers using custom domains may have experienced downtime. Once we identified the root cause of the issue, we took swift action to resolve it. We have verified that the service is now fully restored and...

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

Affected: HTTP Pages, HTTPS Pages

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. monitoring 2025-10-24 04:06 UTC

   We have identified a change which affected the availability of public status pages with custom domain. The change has been rolled back and we are monitoring.

2. monitoring 2025-10-24 04:15 UTC

   We are continuing to monitor for any further issues.

3. resolved 2025-10-24 04:22 UTC

   We identified a configuration change to our edge networking that affected our ability to route traffic for Public Statuspages that use a custom domain. This occurred from 02:55 to 03:13 UTC, at which point the issue was rectified. During this period, the ability to view these...

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

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. resolved 2025-10-20 08:00 UTC

   Atlassian Cloud services were impacted due to an incident with our public cloud provider. During this issue, Atlassian's internal services were affected which could have led to intermittent issues while logging into manage.statuspage.io for some of our customers. This issue is...

2. postmortem 2025-10-28 05:43 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 Statuspage's status page.

Affected: HTTP Pages, Web Portal, HTTPS Pages, Public API

Failure mode: Network, DNS, routing or connectivity 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).

Names an upstream provider: Cloudflare.

1. investigating 2025-02-13 19:22 UTC

   We are currently investigating this issue.

2. investigating 2025-02-14 07:07 UTC

   We are continuing to investigate this issue.

3. identified 2025-02-19 09:55 UTC

   We have determined that the connectivity issue is due to a DNS name resolution problem affecting certain ISPs in Brazil, which are unable to resolve *.statuspage.io domains. This issue does not impact all Brazilian customers and subscribers; it varies depending on the customer's...

4. identified 2025-02-20 15:43 UTC

   Please follow the steps mentioned in the below link to mitigate the DNS issues in Brazil for statuspage.io domains: https://community.atlassian.com/t5/Statuspage-articles/Mitigation-steps-for-statuspage-io-domain-ISP-Issues-in-Brazil/ba-p/2951025#M274

5. identified 2025-02-25 14:29 UTC

   We are actively working with ISPs to resolve the current issues and to better understand the recent changes that have contributed to these problems. We also encourage our customers to contact their ISPs, as this appears to be an ISP-specific issue. Our investigation show that...

6. resolved 2025-03-11 07:52 UTC

   After a thorough investigation, we have determined that the recent connectivity issues experienced for statuspage.io domains in Brazil were isolated to specific Internet Service Providers (ISPs) within Brazil and there was no impact or issue with Statuspage’s infrastructure and...

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

Affected: HTTP Pages, Web Portal, Email, HTTPS Pages, Authenticated API, SMS, Status Embed Widget, DNS Validation, Webhook, SSL Provisioning, Public API, Twitter, Billing, Shortlinks, SMS Subscription

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 2024-11-09 09:28 UTC

   We are investigating server errors. We have isolated the problem and applied the fix.

2. monitoring 2024-11-09 09:39 UTC

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

3. resolved 2024-11-09 10:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Atlassian Statuspage'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-06-28 03:09 UTC

   We are aware of error messages displayed by the Statuspage JSM plugin. The team is currently investigating the issue.

2. identified 2024-06-28 04:07 UTC

   The issue has been identified, and we will be fixing it shortly.

3. resolved 2024-06-28 04:37 UTC

   This issue has been resolved.

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

Affected: Signup

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 low confidence (taxonomy v0.2).

1. monitoring 2024-06-03 23:26 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. In the meantime, we have enabled the alternative login option for Statuspage, so that our customer can still log...

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

   This incident has been resolved.

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

Affected: Authenticated API, Public API

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-03-13 08:00 UTC

   We are currently investigating this issue.

2. identified 2024-03-13 08:25 UTC

   The issue has been identified, and a fix is in progress.

3. monitoring 2024-03-13 08:47 UTC

   A fix has been implemented, and we are monitoring the results. The API has fully recovered.

4. resolved 2024-03-13 10:27 UTC

   This issue has been resolved.

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

Affected: HTTP Pages, Admin User+Pass, Web Portal, Statuspage, Pingdom Email, Email, Pingdom Integration, Ticketing, HTTPS Pages, Admin Google Auth, Authenticated API, External, New Relic Email, Slack, SMS, Knowledge Base, Status Embed Widget, Admin SAML 2.0, DNS Validation, Generic Email, Webhook, New Relic Integration, API Documentation, SSL Provisioning, Public API, Page Access Users, PagerDuty Webhook, Twitter, Datadog Integration, Metastatuspage, Page Google Auth, Billing, Custom Integration, Shortlinks, Jira Software Integration, Marketing Site (www.statuspage.io), Page SAML 2.0, SMS Subscription, Page IP Restriction, 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-05 18:36 UTC

   We are investigating an issue where we are facing intermittent issues while provisioning Statuspage.

2. resolved 2024-02-05 21:00 UTC

   We have identified and fixed the issue and now Statuspage provisioning is working for our customers.

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

Affected: Status Embed Widget

Failure mode: CDN or edge layer failed or served bad content. 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-11-17 16:37 UTC

   We are investigating an intermittent issue reported by a few customers about wrong data shown in the status embed frame in their sites. We are investigating this issue currently and will share updates soon.

2. resolved 2023-11-17 17:25 UTC

   There was an intermittent error with status embed page where cached responses were incorrectly being shown to a few customers. This is resolved as of now.

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

Affected: HTTP Pages, HTTPS Pages, Public API

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-10-28 07:36 UTC

   We are currently seeing intermittent errors in viewing public Statuspages. We are investigating this problem and will provide updates shortly

2. monitoring 2023-10-28 07:55 UTC

   Update: We have fixed the issue and are monitoring actively

3. resolved 2023-10-28 08:01 UTC

   Issue is now resolved and everything is back to normal working state.

4. postmortem 2023-11-06 09:25 UTC

   ### **SUMMARY** From 06:00 UTC to 07:45 UTC on October 28, 2023, Atlassian customers using Statuspage had intermittent issues with all Statuspage functionality. The event occurred due to a database performance issue during a [scheduled database...

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

Affected: HTTP Pages, HTTPS Pages, Status Embed Widget

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-09-18 18:50 UTC

   We are investigating cases of degraded performance for public pages. Pages may be failing to load or loading more slowly than normal.

2. monitoring 2023-09-18 19:16 UTC

   We have identified the issue and a fix has been implemented. We have scaled our services to mitigate the issue and are monitoring the results.

3. resolved 2023-09-18 19:19 UTC

   This incident has been resolved.

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

Affected: Web Portal

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. investigating 2023-09-13 14:16 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:33 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:42 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:37 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:37 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-10-06 15:19 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 Statuspage's status page.

Affected: Web Portal, Billing, Signup

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. identified 2023-08-30 05:03 UTC

   We have identified issues with our login system. To unblock customer login we have temporarily enabled alternate login flows for the manage portal. We will continue to monitor the situation and provide further details as we investigate further.

2. resolved 2023-08-30 06:16 UTC

   This incident has been resolved.

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

Affected: Web Portal

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 09:18 UTC

   We are investigating reports of intermittent errors during login for some customers using Statuspage. We will provide more details once we identify the root cause.

2. identified 2023-07-06 09:28 UTC

   We have identified issues with our login system. To unblock customer login we have temporarily enabled alternate login flows for the manage portal. We will continue to monitor the situation and provide further details as we investigate further.

3. monitoring 2023-07-06 13:14 UTC

   A fix has been implemented, we are seeing recovery and continuing to monitor the incident.

4. resolved 2023-07-06 13:26 UTC

   This incident has been resolved.

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

Affected: HTTP Pages

Failure mode: CDN or edge layer failed or served bad content. 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-15 08:09 UTC

   We have identified an unintended issue with redirecting http to https for a tiny cohort of customers on SSL-enabled custom domains. This does not affect the availability of any Statuspage on a custom domain with SSL enabled - they are available via https:// .

2. identified 2023-06-16 08:50 UTC

   We are in the process of rolling out a fix for impacted domains.

3. resolved 2023-06-16 17:31 UTC

   This incident has been resolved.

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

Affected: Web Portal

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-05-31 08:20 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2023-05-31 10:17 UTC

   This incident has been resolved.

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

Affected: SMS

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-06 15:52 UTC

   We are currently investigating the issue.

2. investigating 2023-04-06 18:24 UTC

   Issue seems intermittent and we are continuing to investigate this issue.

3. resolved 2023-04-06 19:17 UTC

   This incident is resolved.

Excerpts are shortened. Read the full incident on Atlassian Statuspage'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. resolved 2023-03-22 15:30 UTC

   Between 9:09 PM PST on March 22nd and 9:46 PM PST on March 23rd, there was an issue preventing new signups for Statuspage. Customers attempting to sign up during that time may have encountered difficulties. We have since identified and resolved the issue, which only affected new...

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

Affected: HTTPS Pages

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 2023-03-20 19:54 UTC

   We are noticing some slowness/intermittent errors while loading some public pages. We are investigating the errors.

2. monitoring 2023-03-20 20:28 UTC

   Systems seem stable and we are monitoring now

3. resolved 2023-03-20 21:06 UTC

   This has been resolved.

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

Affected: Web Portal

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-02-27 16:06 UTC

   We are currently experiencing an issue with uploading images on manage portal.

2. resolved 2023-02-27 18:57 UTC

   This incident has been resolved.

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

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. resolved 2023-02-21 18:00 UTC

   We experienced a delay in delivery of notifications of incidents for a period of 15 minutes which has been resolved. We have identified the cause of this is an ongoing incident with one of our messaging vendors, and we have migrated all possible notification traffic to our...

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

Affected: Page Google Auth, Page SAML 2.0

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 high confidence (taxonomy v0.2).

1. investigating 2023-02-14 12:32 UTC

   We are currently investigating the issue.

2. monitoring 2023-02-14 14:09 UTC

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

3. resolved 2023-02-14 14:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Atlassian Statuspage'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. resolved 2023-02-08 19:26 UTC

   The manage portal was out of service between 11:21-11:25 AM PST. The problem has resolved itself and we have returned to normal operations.

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

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

1. resolved 2022-11-22 20:30 UTC

   Our API service experienced an abnormal number of timeouts affecting 0.6% of total traffic due to DNS errors between 12:30-1:10 pm PST.

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

Affected: Email, SMS, Webhook, Twitter

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. identified 2022-11-09 22:37 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2022-11-09 22:59 UTC

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

3. resolved 2022-11-09 23:10 UTC

   This incident has been resolved. All notifications have been processed. No notifications were lost.

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

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2022-09-28 00:00 UTC

   Between 5:09 to 5:13 PM PST, public status pages experienced elevated errors due to increased traffic.

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

Affected: Billing

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-09-12 16:06 UTC

   A subset of Statuspage customers are unable to access the Billing page within Statuspage. We are currently investigating the issue.

2. identified 2022-09-12 16:30 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2022-09-12 17:03 UTC

   Billing page access should be restored for all customers. We are continuing to monitor the issue.

4. resolved 2022-09-12 20:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Atlassian Statuspage'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. resolved 2022-08-02 00:00 UTC

   Between 4:55pm and 10:10pm PST, users were not able to subscribe via email to statuspages. We have identified the root cause and have resolved the issue.

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

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. resolved 2022-07-21 17:20 UTC

   A recent deploy was found to contain errors. Our infrastructure has been successfully rolled back to a previous version of the code, and traffic is being served as normal again.

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

Affected: SMS Subscription

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-07-21 16:37 UTC

   We are currently investigating this issue.

2. resolved 2022-07-21 16:49 UTC

   We have resolved issue.

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

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2022-07-18 11:30 UTC

   Due to elevated traffic, we experienced intermittent timeouts and errors in serving public pages between 4:24 to 4:25 AM PST. In response, we have implemented updates to our services to mitigate the same issue in the future.

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

Affected: Web Portal

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 high confidence (taxonomy v0.2).

1. investigating 2022-06-27 00:01 UTC

   We are currently investigating failed logins when users are accessing Statuspage's manage portal.

2. investigating 2022-06-27 00:35 UTC

   We are still investigating the root cause of the issue. Users who have attempted to login to manage their Statuspages, should be receiving an email with a login link which they can use to login temporarily instead of the normal login flow.

3. resolved 2022-06-27 01:31 UTC

   This incident has been resolved.

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

Affected: External

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

Names an upstream provider: AWS.

1. investigating 2022-05-16 19:00 UTC

   A number of incorrect emails were sent out saying AWS third party components will no longer receive updates. These components have not been impacted and we are investigating the root cause of the emails now.

2. identified 2022-05-16 19:41 UTC

   We have identified the cause of the emails and are working on a resolution now

3. identified 2022-05-16 20:45 UTC

   We are continuing to work on a fix for the incorrect emails. If any other emails are received about AWS components please disregard them

4. resolved 2022-05-16 22:31 UTC

   This incident has been resolved.

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

Affected: Admin User+Pass, Web Portal

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 2022-05-14 19:16 UTC

   We are currently investigating failed logins when users are accessing Statuspage

2. identified 2022-05-14 19:32 UTC

   We have identified the issue and are working on a resolution now

3. monitoring 2022-05-14 19:48 UTC

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

4. resolved 2022-05-14 20:16 UTC

   This incident has been resolved.

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

Affected: Pingdom Integration, New Relic Integration, Datadog Integration, Custom Integration

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. investigating 2022-04-25 22:47 UTC

   We are currently investigating an issue with missing system metrics for a subset of status pages.

2. identified 2022-04-26 01:54 UTC

   We have identified a metrics display problem for a majority of status pages due to a vendor issue. This is purely a display problem and we are not experiencing any data loss. We are working to return the service to normal operations.

3. identified 2022-04-28 00:50 UTC

   We are still actively engaged with our vendor while their engineering teams work on the issue. Unfortunately, alternative workarounds did not produce acceptable results. Once again, this is purely a display problem and we are not experiencing any data loss.

4. monitoring 2022-04-28 21:46 UTC

   We have released a fix for the metrics display problem. Affected metrics displays should have returned to a functioning state. We are still actively engaged with our vendor and are working with their engineering team on fixing the root cause of this issue.

5. resolved 2022-04-29 16:08 UTC

   This incident has been resolved.

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

Affected: HTTP Pages, Web Portal, HTTPS Pages, Authenticated API

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. identified 2022-04-05 13:45 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2022-04-05 21:11 UTC

   We have partially reactivated the Statuspages of affected customers. The hosted pages should be up, and the API capabilities have been restored so affected customers can use this to manage their pages while work is done to restore access to the manage portal. We have defined two...

3. identified 2022-04-06 21:26 UTC

   We are continuing to work on the resolution of the incidents for some Statuspage, Jira Work Management, Jira Service Management, Confluence, Jira Software, Atlassian Access, Jira Product Discovery, and Opsgenie Cloud customers.

4. identified 2022-04-07 04:19 UTC

   We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues...

5. identified 2022-04-07 09:34 UTC

   We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues...

6. identified 2022-04-07 12:26 UTC

   We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues...

7. identified 2022-04-07 18:43 UTC

   We are beginning partial restoration to a cohort of customers. The early stages of this process will be controlled and hands-on, as we work with customers live to get feedback and ensure that restoration is working correctly before we accelerate the process for the next cohort....

8. identified 2022-04-07 21:51 UTC

   We continue to work on partial restoration to the first cohort of customers. The plan to take a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update.

9. identified 2022-04-08 01:27 UTC

   We continue to work on partial restoration to a cohort of customers. The plan is to take a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update

10. identified 2022-04-08 07:53 UTC

    We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same...

11. identified 2022-04-08 10:59 UTC

    We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same...

12. identified 2022-04-08 15:30 UTC

    We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.

13. identified 2022-04-08 17:11 UTC

    Restoration work to restore sites is underway and will continue into the weekend. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.

14. identified 2022-04-08 20:28 UTC

    Restoration work to restore sites is underway and will continue into the weekend. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.

15. identified 2022-04-09 01:36 UTC

    The team is continuing the restoration process through the weekend and working toward recovery. We are continuously improving the process based on customer feedback and applying those learnings as we bring more customers online.

16. identified 2022-04-09 10:52 UTC

    Our team is working 24/7 to progress through site restoration work. Core functionality has been restored across a number of sites. We are continuously improving the process with the aim of accelerating the restoration process from here.

17. identified 2022-04-09 14:33 UTC

    Our team is working 24/7 to progress through site restoration work. Core functionality has been restored across a number of sites. We are continuously improving the process with the aim of accelerating the restoration process from here.

18. identified 2022-04-09 18:25 UTC

    The restoration process is underway. At this time we have no new significant updates, but the team continues to work around the clock to bring our customers back online.

19. identified 2022-04-09 22:23 UTC

    The restoration process is underway. At this time we have no new significant updates, but the team continues to work around the clock to bring our customers back online.

20. identified 2022-04-10 04:05 UTC

    Our teams are committed to restoring each customer’s service as soon as possible and are working through the weekend toward recovery.

21. identified 2022-04-10 09:35 UTC

    Our teams are committed to restoring each customer’s service as soon as possible and are working through the weekend toward recovery.

22. identified 2022-04-10 13:14 UTC

    We continue to work 24/7 to restore service to affected customers. We have restored partial access for some customers and will be continuing to restore access into next week.

23. identified 2022-04-10 19:45 UTC

    We are still working 24/7 to restore service to affected customers. We have restored partial access for some customers and will be continuing to restore access into next week.

24. identified 2022-04-11 00:50 UTC

    A dedicated team continue to work 24/7 to expedite service recovery. Restoration of all customers remains our top priority. We hear and appreciate all the feedback from our valued customers and are taking every necessary step to both restore full service and ensure site...

25. identified 2022-04-11 09:01 UTC

    A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are...

26. identified 2022-04-11 12:11 UTC

    A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are...

27. identified 2022-04-11 16:04 UTC

    A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are...

28. identified 2022-04-12 13:48 UTC

    The team is moving through the restoration process this week and is accelerating toward recovery. Functionality for 40% of impacted users has been restored.

29. identified 2022-04-14 15:53 UTC

    We have restored functionality for 49% of users impacted by the outage. We are taking a batch-based approach to restoring customers, and to-date, this process has been semi-automated. We are beginning to shift towards a more automated process to restore sites. That said, there...

30. identified 2022-04-14 20:14 UTC

    We have now restored functionality for 53% of users impacted by the outage. As outlined in yesterday’s update, we are restoring affected customers using a three step process: 1. Technical restoration of affected sites 2. Internal validation of restored sites 3. Validating with...

31. identified 2022-04-15 03:06 UTC

    We have now restored functionality for 55% of users impacted by the outage. With automation in full effect, we have significantly increased the pace at which we are conducting technical restoration of affected customer sites, and we have reduced the time required for the...

32. identified 2022-04-15 20:13 UTC

    We have made significant progress over the last 24 hours and have now restored functionality for 62% of users impacted by the outage. We have also doubled the size of the batches we are pushing through the restoration process, which was a result of optimizing automated processes...

33. identified 2022-04-16 01:42 UTC

    We have now restored 78% of users impacted by the outage as we continue to move with more speed and accuracy. Our teams will continue to restore sites through the weekend, and we expect to have all sites restored no later than end of day Tuesday, April 19th PT. As we restore...

34. identified 2022-04-16 20:12 UTC

    We have now restored 85% of users impacted by the outage and will continue to get sites back to customers for validation, over the weekend. As we hand your restored site over to you for validation, please reach out to our teams should you find any issues so that our support...

35. identified 2022-04-17 04:19 UTC

    We have now restored 99% of users impacted by the outage and have reached out to all affected customers. Our teams are available to help customers with any concerns. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have...

36. monitoring 2022-04-17 19:12 UTC

    We have restored impacted Statuspage customer sites and the service is operating normally. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have any trouble accessing your support ticket, contact us at...

37. resolved 2022-04-17 22:06 UTC

    We have restored impacted Statuspage customer sites and the service is operating normally. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have any trouble accessing your support ticket, contact us at...

38. postmortem 2022-04-29 20:34 UTC

    Earlier this month, several hundred Atlassian customers were impacted by a site outage. We have published a Post-Incident Review which includes a technical deep dive on what happened, details on how we restored customers sites, and the immediate actions we’ve taken to improve...

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

Affected: Pingdom Integration, New Relic Integration, Datadog Integration, Custom Integration

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 2022-03-30 22:07 UTC

   System metrics is experiencing a delay of up to 5 to 10 minutes. We are currently investigating this issue.

2. identified 2022-03-31 00:05 UTC

   We have identified the issue and we’re working with our vendor to return the service to normal operations.

3. identified 2022-03-31 19:18 UTC

   Based on additional reporting and investigation, we have found that System Metrics is experiencing delays between 5 to 30 minutes. We are continuing to work with our vendor to return the service to normal operations.

4. monitoring 2022-03-31 23:18 UTC

   We have identified and resolved all issues with third-parties and we are now monitoring and continuing to process any delayed metrics.

5. resolved 2022-04-01 00:51 UTC

   This incident has been resolved.

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

Affected: Admin User+Pass

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

Names an upstream provider: AWS.

1. monitoring 2022-03-14 14:10 UTC

   We have identified and mitigated an issue with users logging in to Statuspage starting at 6:05am PST and ending at 6:46am PST and are monitoring the results.

2. resolved 2022-03-14 14:28 UTC

   This incident has been resolved.

3. postmortem 2022-03-22 15:58 UTC

   ### **SUMMARY** On March 14, 2022, between 01:05pm and 01:47pm UTC, some Atlassian customers were unable to login to our products including Trello and Statuspage, and could not access some services including the ability to create support tickets. The underlying cause was a newly...

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

Affected: HTTP Pages, HTTPS Pages, Status Embed Widget, Public API

Failure mode: CDN or edge layer failed or served bad content. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2022-03-09 04:08 UTC

   Content changes to public status pages (e.g. incident creation and updates) were delayed by up to 15 minutes, for changes that were made beginning Mar. 4, 1pm PST. Users may have briefly seen out-of-date content when viewing public status pages during this time. A bug was...

2. identified 2022-03-09 04:23 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2022-03-09 05:17 UTC

   This incident has been resolved.

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

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2022-02-07 18:00 UTC

   Increased load caused API service to experience errors from 10:03 - 10:15 PST.

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

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2022-01-26 13:57 UTC

   Due to elevated traffic, we experienced intermittent timeouts and errors in serving public pages between 5:57 and 5:58 AM PST. We have made updates to our services to prevent similar problems from happening.

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

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 low confidence (taxonomy v0.2).

1. resolved 2022-01-10 13:30 UTC

   Between 5:20 to 5:24 AM PST, a slow performing API query resulted in an elevated number of 500 errors on the manage portal. The root cause of the degraded performance has been identified and a fix has been deployed. The manage portal is now operating normally.

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

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

1. identified 2022-01-05 23:39 UTC

   A data migration erroneously dropped indexes that were still in use, causing decrease in availability for a subset of all inbound requests.

2. resolved 2022-01-06 00:11 UTC

   This incident has been resolved.

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