Atlassian StatuspageIssues displaying system metrics
New System metrics implementation has been successfully enabled for all customers.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
New System metrics implementation has been successfully enabled for all customers.
Resolved
This incident has been resolved.
Resolved
Metrics collection continues to operate normally in US-West-2, and full metrics collection has been fully restored with no blips in stability.
Resolved
This incident has been resolved.
Resolved
All services were restored and fully operational on February 21, 2026, at 23:42 UTC.
Resolved
This incident has been resolved.
Resolved
Our authentication provider has concluded the incident, citing that authentication is functioning as expected. Docker authentication remains stable.
Resolved
The issue affecting one server in our German storage array has been fully resolved. All services are now operating normally. We will continue monitoring to ensure stability.
Resolved
Severity Level: [Medium] The incident has been resolved. Launches in Utah (us-west-3) should now work as expected.
Resolved
The service is still healthy and this incident has been resolved.
Resolved
The issue causing delays in recurring Custom Agent triggers has been fully resolved.All systems are operating as expected, and the backlog has been cleared.
Resolved
All services are back to normal operations
Resolved
The incident has been resolved and services are now operating as expected. We will continue to monitor the situation, but no further impact is anticipated.
Resolved
On February 20, 2026, between 1:44 PM and 8:27 PM EST, an Airtable outage caused authentication errors and trigger delays for customers using Airtable integrations through Zapier. Affected Airtable authentications were marked as inactive, resulting in errors and delays for impacted automations. The Zapier platform remained fully operational throughout. Airtable's services have since fully recovered. If you are still experiencing issues with your Airtable connections, please visit the Zapier Connections page to reconnect Airtable, and check your Zap History to replay any affected runs.
Resolved
Impact Trello users are experiencing issues with websocket connections, leading to difficulties in maintaining active sessions. Affected users may notice disruptions in service as connections are intermittently dropping. Current Status Efforts are underway to restore normal service. Teams are actively engaged in identifying the best path to full resolution. Next Steps The incident team is focusing on pinpointing the root cause and implementing necessary fixes. The next communication will be shared in 30 minutes.
Resolved
All systems operational. We apologize for the disruption this issue caused. We are committed to the reliability of all ClickHouse Cloud services and appreciate your understanding as we continue to improve our systems and operations. If you have questions or need information on a specific ClickHouse service, please contact support "contact support": https://clickhouse.cloud/support.
Resolved
Severity Level: [High] The incident has been resolved. Services in AUS01 (us-south-3) region is now working as expected.
Resolved
Performance for the Duo Agent Platform in Europe has been restored to normal. For more information, please see: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21352
Resolved
Our recovery is complete, and Airtable's service is back to normal.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.
Resolved
Things have remained stable, and we are confident that things are now resolved. The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved
Resolved
Ingest performance has remained stable following mitigation. We are no longer observing impact.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This issue is fully resolved now - customers that were affected should have tests passing as expected now and previous failures are invalidated.
Resolved
Form notification emails were not delivered as expected between 14:15 and 16:41 UTC due to an issue with an upstream provider. All queued emails from this period have since been successfully processed and delivered. Form submissions themselves were not impacted and remained accessible via the Forms tab in site settings throughout the incident. We’re no longer seeing any impact, and this incident is now resolved. Thank you for your patience while we worked to restore normal delivery.
Resolved
This incident has been resolved.
Resolved
A fix has been implemented which fixed the issue. All operations should have resumed normally.
Resolved
On February 13, 2026, between 21:46 UTC and 22:58 UTC (72 minutes), the GitHub file upload service was degraded and users uploading from a web browser on GitHub.com were unable to upload files to repositories, create release assets, or upload manifest files. During the incident, successful upload completions dropped by ~85% from baseline levels. This was due to a code change that inadvertently modified browser request behavior and violated CORS (Cross-Origin Resource Sharing) policy requirements, causing upload requests to be blocked before reaching the upload service.<br /><br />We mitigated the incident by reverting the code change that introduced the issue.<br /><br />We are working to improve automated testing for browser-side request changes and to add monitoring/automated safeguards for upload flows to reduce our time to detection and mitigation of similar issues in the future.
Resolved
This incident has been resolved.
Resolved
Collections in EU are fully working now.
Resolved
This issue has been resolved and all services are functional.
Resolved
This issue has been resolved and all services are functional.
Resolved
Network traffic in LHR has been stable for some time now, we are not seeing any further issues.
Resolved
This incident has been resolved.
Resolved
The service has been stable for the past 90 minutes. The issue has been resolved. https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21340
Resolved