ChatGPT / OpenAIHigh error rate for Dall-e
All impacted services have now fully recovered.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
All impacted services have now fully recovered.
Resolved
All impacted services have now fully recovered.
Resolved
Authentication services remain stable. We are continuing to work directly with the affected customers on client-specific issues unrelated to Docker services.
Resolved
All impacted services have now fully recovered.
Resolved
Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Resolved
This incident has been resolved.
Resolved
The search backlog has been flushed and updates are processing at the usual speed
Resolved
From 5:30 PM to 6:30 PM UTC, some users were experiencing issues when publishing Figma Make files or publishing Sites. This has been resolved.
Resolved
We've confirmed that the console is back to consistent, normal operation, and we're closing this incident.
Resolved
This incident has been resolved.
Resolved
ESM has resolved their issue. All function deploy actions should now be working.
Resolved
This issue is now resolved and all MCP functionality should return to normal. Thank you for your patience, and if you are still running into any issue, please reach out to Support for assistance: https://zapier.com/app/get-help
Resolved
Final monitoring of the eu-iceland1-a storage cluster has been successfully completed, and all services remain stable. All planned recovery activities and software upgrades are finished, with performance and VM operations restored to normal levels. This incident is now resolved.
Resolved
The incident is now resolved and the system is full operational. The issue started at 16:56:16 UTC and ended at 16:57:31 UTC. The Event API caches event keys for a duration so not all requests would have been effected with sending events, but some may have. Our SDKs automatically retry up to 5 times with backoff, but due to the time window being >60s, many retries might have failed as well. Our REST API and dashboards returned once the connections were re-established. The cause of this incident is related to a networking issue that we are working on follow up mitigation efforts to avoid this issue from happening again.
Resolved
Between 13:55 UTC and 15:45 UTC January 07, 2026, customers may have experienced failures or delays in database connectivity. The issue has been fully resolved. All affected components are operating normally again.
Resolved
This incident affecting Canvas Copilot has been resolved. Between approximately 4:00 PM UTC on January 5, 2026 and 11:00 AM UTC on January 7, 2026, some users experienced intermittent errors when using Copilot in Canvas. The service has since returned to normal operation, and there is no longer any customer impact. If you have questions or need assistance, please contact our support team: https://zapier.com/app/get-help
Resolved
Available browsers and session fulfillment has recovered. We appreciate your patience. Please contact customer support if you continue to experience degraded session availability.
Resolved
All services are working normally
Resolved
We’ve resolved the issue that caused lovable.dev "lovable.dev": http://lovable.dev to return “internal server error” responses. Service has been restored and we’re monitoring to ensure everything remains stable.
Resolved
This incident has been resolved.
Resolved
Loading times should be back to normal.
Resolved
Loading times should be back to normal.
Resolved
We experienced a degraded performance on our Payments products. You may have experienced delays in EUR Payment settlement. The service has recovered and payments are settling in a timely manner. Impact end time: 07/01/2026, 08:00 UTC Impact end time: 07/01/2026, 08:32 UTC Client actions: None
Resolved
We have successfully mitigated the incident and the affected service is now fully operational. Our teams have verified that normal functionality has been restored. Thank you for your patience and understanding while we worked to resolve this issue.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The engineering team has investigated the issue, identified the root cause, and implemented a fix. The degradation should now be resolved and all systems should be fully operational.
Resolved
The delays with balanced assignment have been resolved. They started at 14.00 UTC and were resolved at ~17.40 UTC. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
This incident is resolved.
Resolved
### Summary On December 12, 2025, between 05:31 UTC and 07:11 UTC, Trello customers experienced errors or slow loading times due to a dependency library upgrade that caused high resource usage. The incident was detected within 1 minute by the automated monitoring system and mitigated by rolling back the version of the dependency library which put Atlassian systems into a known good state. The total time to resolution was 1 hour and 41 minutes. ### **IMPACT** The issue caused service disruption for all Trello customers on December 12, 2025 between 05:31 UTC and 07:11 UTC. Users experienced degraded service between 05:31 UTC and 06:32 UTC, and most users were unable to load Trello between 06:32 UTC to 07:07 UTC. ### **ROOT CAUSE** The issue was caused by an upgrade to a dependency library. As a result, there was an increase in system memory consumption causing startups to take longer than expected. When the startup time exceeded the allowed threshold, the worker process was flagged as unresponsive and restarted as an automated recovery action. Because every worker on the instance failed to startup within the expected time, the instance entered a startup loop that required intervention. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have several testing and preventive processes in place, we didn’t anticipate that the upgrade would consume more memory, which ultimately caused the startup failure loop and service disruption. We are prioritizing the following improvement actions designed to avoid this issue in the future: * Review our automated detection of unresponsive workers and adjust the detection thresholds during initialization. * Improve monitoring during workers startup and restarts due to unresponsiveness. * Enhance the stricter standard process for confirming memory/other data processing resource requirements for planned updates. 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
No further issues have been experienced and all services are operating normally. The incident is now resolved.
Resolved
This incident has been resolved.
Resolved
On January 6th, 2026 at UTC 12:00, we experienced an approximately 50-minute service disruption affecting customers in non-US regions. During this time, some requests may have failed or timed out. What Happened: During routine maintenance, we upgraded a core infrastructure component. While the upgrade itself completed as expected, some services did not successfully reconnect to the updated infrastructure. This led to temporary communication issues and degraded service in the affected regions. We apologize for the inconvenience and want to assure you that we are taking steps to help prevent similar issues in the future.
Resolved
All impacted services have now fully recovered.
Resolved
The load has dropped down to normal after the fix. All systems are now operational. More details can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21046.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved