GhostReduced performance on Ghost(Pro)
All Ghost sites are back to normal
Resolved
Outages and recoveries from the services you depend on.
40 incidents
All Ghost sites are back to normal
Resolved
This issue has been resolved.
Resolved
This incident has been resolved.
Resolved
Current status: The Slack engineering team investigated connectivity issues that affected some users between approximately 13:30 and 14:00 UTC on June 2, 2026. The issue has been resolved and no further impact has been reported. Scope: Some users, primarily in Europe, may have experienced difficulty loading or sending Slack messages during this window We apologize for any inconvenience this may have caused.
Resolved
The incident has been resolved, all systems have returned to normal.
Resolved
This incident has been resolved.
Resolved
The issue affecting Wizard authorization calls has been resolved. The fix has been deployed and we have confirmed normal operation.
Resolved
We think the impact from the issue is over, however, uploads using 3rd cloud providers (Google Drive, Instagram, Box, Dropbox etc) are temporarily disabled.
Resolved
All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.
Resolved
The issue has been resolved, and the cluster is fully operational again. Please let us know if you continue to experience any issues.
Resolved
This issue should be resolved now and mobile transcriptions should be completed as normal. Apologies for any disruption!
Resolved
We have identified the issue and local evaluations with groups should now evaluate correctly.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
We're pleased to inform you that the issue affecting X/Twitter Streams in Hootsuite has been successfully resolved. Our engineering team has verified the fix, and users should now be able to load their X/Twitter Streams without encountering errors. Thank you for your patience throughout this incident!
Resolved
This incident has been resolved.
Resolved
The incident has been resolved. The root cause of the problem was a GCP incident affecting I/O on certain VM types in one of the zones we are using. As a result, some nodes in our clusters were affected.
Resolved
Between 06:00-07:00 UTC, we saw increased numbers of API errors in the EU region. The largest impact was between 06:46-07:00. We've implemented a fix and we're no longer seeing elevated errors.
Resolved
This incident has been resolved.
Resolved
We have resolved an issue affecting the Payroll Superannuation and Settings page, where customers were experiencing page loading failures and errors. The issue was caused by a network fault within our Payroll environment. Our technical team has remediated the fault and restored full service. We apologise for the inconvenience caused.
Resolved
We're now caught up and events are being processed normally.
Resolved
Our team has resolved the issue impacting customers trying to access invoicing in Xero. We apologise for any inconvenience this has caused. A product release caused invoicing to become unavailable. We learn from every incident and put measures in place to prevent issues from happening again.
Resolved
The issue has been resolved. All impacted systems are now operating normally. Dashboard logins are now resolved.
Resolved
Front is continuing to partner with Microsoft on root cause of remaining channel sync failures. We added the ability to automatically bring these channels back online to prevent further customer impact.
Resolved
This incident has been resolved.
Resolved
Updates are back to normal, and we are load testing the planned migration more comprehensively before attempting it again.
Resolved
This incident has been resolved.
Resolved
### Summary ### On May 12, 2026 between 19:01 and 20:46 UTC, a subset of Atlassian customers may have experienced delays in background operations and automation processes. Some background operations, such as notifications or search indexing, were delayed until May 14, 2026 19:25 UTC due to increased cross-region traffic. The issue stemmed from a latent bug in the event processing pipeline. Automated monitoring detected the incident within 16 minutes, and it was mitigated through manual rollback within 1 hour and 45 minutes. Recovery of cross-region event delivery from the affected timeframe took 48 hours due to infrastructure scale constraints. ### IMPACT ### During the incident, customers may have experienced delays in background operations like automation, search indexing, notifications, and permission synchronization. The event processing pipeline distributes events between Atlassian services to support these background operations. - On May 12, 2026, at 19:01 UTC, the deployment of a routing configuration increased event volume across cross-region services. At 20:46 UTC, rolling back routing configurations resolved the issue. - Processing the accumulated cross-region message backlog finished by May 14, 2026, at 19:25 UTC. **Automation & Jira Service Management** Some Atlassian customers experienced event-triggered rules delayed or executed multiple times during the recovery window. **Confluence** Some Atlassian customers experienced delays in search indexing and possible duplicate notifications and automation rule executions during the recovery window. ### ROOT CAUSE ### The issue arose from the deployment of a routing configuration change to the event processing platform, exposing a latent bug in legacy configurations. This change distributed higher volume of events to cross-region services. Cross-region services validated and discarded extra events but needed greater scale to handle the increased influx. The mitigation involved rolling back the configuration change in the event platform. Recovery involved scaling cross-region services to handle higher inbound traffic. ### REMEDIAL ACTIONS PLAN & NEXT STEPS ### We know that performance degradations impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified because the change was related to a very specific kind of legacy case that was not picked up by our automated continuous deployment suites and manual test scripts. We are prioritizing the following improvements to help prevent similar incidents in future: - Enhance runtime metrics across critical-path configurations to predict change impact before deployment. - Enhance failover capabilities to create and replace infrastructure components to respond faster to increased processing demands. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
This incident was resolved about 1:29pm CT. No further impact has been observed.
Resolved
The issue has been resolved and Lovable is back to normal.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Our systems have been stable since Friday, May 29th. We're monitoring closely and improving spike detection to prevent recurrence and adding proactive capacity monitoring to detect admin dashboard degradation before it impacts customers. Full root cause analysis coming soon. Thanks for your patience and understanding.
Resolved
The source of the issue has been identified and fixed
Resolved
On May 28th, 2026, between approximately 18:27 and 20:41 UTC, the GitHub Copilot service was degraded due to an issue with the Responses API of an upstream provider affecting the GPT-5.2, GPT-5.3-Codex, GPT-5.4, and GPT-5.5 models. Requests routed to these models via the Responses API returned elevated error rates, which also affected Copilot coding agent and Copilot code review. No other models were impacted. <br /><br />We mitigated the incident by shifting traffic away from the affected models while the upstream provider deployed a fix. <br /><br />GitHub is working to improve automated failover for the affected models and strengthen monitoring to prevent similar incidents in the future.
Resolved
Posts and pages are updating as normal again.
Resolved