Incident History

Partial outage while accessing statuspage

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 operational. Our team is closely monitoring the situation to ensure continued stability. We will conduct an internal review of this incident and implement necessary improvements to our systems to prevent or reduce the likelihood of similar occurrences in the future.

1761734237 - 1761734237 Resolved

Intermittent errors while accessing public Statuspages

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 status pages was unavailable, but the ability to manage them remained functional, ensuring that no updates or notifications were lost.

1761278770 - 1761279731 Resolved

Atlassian Cloud Services impacted

On October 20, 2025, Atlassian cloud services were impacted by an outage from a third-party provider, Amazon Web Services (AWS). While we have since resolved the immediate impact on our services, our teams are continuing to work on a full Post-Incident Review (PIR).

AWS has published their summary of the event, which you can find here: AWS Incident Summary.

We are continuing our own thorough internal investigation to understand the full impact on Atlassian services and to identify corrective actions to help prevent similar occurrences in the future.

We are committed to transparency and will publish our public PIR on our Statuspage once this investigation is complete. We expect to publish this within the next 30 days.

We sincerely apologize for the disruption this incident caused you and your teams. We appreciate your patience as we complete our review.

1761040089 - 1761040089 Resolved

statuspage.io domain not resolving in Brazil region for some users

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 DNS configurations itself. Our team is actively monitoring the situation and trying our best to reach out to the relevant ISPs to ensure that access issues are resolved for all affected users. If connectivity issues persist, and you are located in Brazil, we kindly ask that you open a support request with your internet service provider or follow our community post to resolve the issue.

https://community.atlassian.com/forums/Statuspage-articles/Mitigation-steps-for-statuspage-io-domain-ISP-Issues-in-Brazil/ba-p/2951025#M274

1739474521 - 1741679540 Resolved

Elevated Server Errors across Statuspage Services

This incident has been resolved.

1731144486 - 1731147001 Resolved

Errors on the Statuspage JSM plugin

This issue has been resolved.

1719544193 - 1719549452 Resolved

Error responses across multiple Cloud products

This incident has been resolved.

1717457181 - 1717460040 Resolved

Statuspage API is facing intermittent issues

This issue has been resolved.

1710316817 - 1710325621 Resolved

Statuspage product provisioning failing intermittently

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

1707158168 - 1707166835 Resolved

Intermittent issues in incidents shown in Status embed frame

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.

1700239046 - 1700241926 Resolved
⮜ Previous