ChatGPT / OpenAIIssues with Increased Codex Usage Rate
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
This issue is now resolved.
Resolved
We have confirmed fully restored functionality of the voice of "George".
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
Help Scout access has now been restored for customers in the Philippines. We will continue to monitor the situation. If you're still experiencing any issues accessing the platform, please let us know.
Resolved
This incident has been resolved.
Resolved
This issue is now resolved.
Resolved
If a pipeline still appears stuck, please cancel and retry the affected job or pipeline. Protections deployed during this incident will prevent this in new pipelines. See https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21462 for complete details.
Resolved
On March 5, 2026, between 12:53 UTC and 13:35 UTC, the Copilot mission control service was degraded. This resulted in empty responses returned for users' agent session lists across GitHub web surfaces. Impacted users were unable to see their lists of current and previous agent sessions in GitHub web surfaces. This was caused by an incorrect database query that falsely excluded records that have an absent field.<br /><br />We mitigated the incident by rolling back the database query change. There were no data alterations nor deletions during the incident.<br /><br />To prevent similar issues in the future, we're improving our monitoring depth to more easily detect degradation before changes are fully rolled out.
Resolved
Both regions are now working as usual.
Resolved
This incident has been resolved.
Resolved
From approximately 10:10am to 10:28am PT we experienced longer-than-usual processing times for transcription of pre-recorded audio. The root cause of this slowdown has been identified and resolved, and response times are back within normal ranges. Our team will continue to monitor traffic to ensure continued good performance.
Resolved
We are able to confirm that the issues with accessing the Hootsuite Dashboard have been resolved. Our team has also confirmed that no customer accounts were impacted during the downtime. If you have any questions or concerns, feel free to contact our Customer Support team. Thank you for your understanding.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
A configuration was changed, and accounts.dev "accounts.dev": http://accounts.dev is resolving correctly again! We're continuing to monitor if there are any anomalous traffic or behavior.
Resolved
This incident has been resolved.
Resolved
On Mar 5, 2026, between 16:24 UTC and 19:30 UTC, Actions was degraded. During this time, 95% of workflow runs failed to start within 5 minutes with an average delay of 30 minutes and 10% workflow runs failed with an infrastructure error. This was due to Redis infrastructure updates that were being rolled out to production to improve our resiliency. These changes introduced a set of incorrect configuration change into our Redis load balancer causing internal traffic to be routed to an incorrect host leading to two incidents. <br /><br />We mitigated this incident by correcting the misconfigured load balancer. Actions jobs were running successfully starting at 17:24 UTC. The remaining time until we closed the incident was burning through the queue of jobs. <br /><br />We immediately rolled back the updates that were a contributing factor and have frozen all changes in this area until we have completed follow-up work from this. We are working to improve our automation to ensure incorrect configuration changes are not able to propagate through our infrastructure. We are also working on improved alerting to catch misconfigured load balancers before it becomes an incident. Additionally, we are updating the Redis client configuration in Actions to improve resiliency to brief cache interruptions.
Resolved
This incident has been resolved.
Resolved
Between 16:05 UTC and 16:26 UTC March 06, 2026, customers may have experienced failures or delays in compute operations or database connectivity. The issue has been fully resolved. All affected components are operating normally again.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We investigated the reports and determined there was no underlying system issue. The affected cases were isolated and are being resolved. Preview generations and deployment updates are operating normally.
Resolved
Between 7:25pm and 8:00pm UTC on February 26th, a very small number of hosted sites experienced an increase in unexpected 404 errors when accessing site pages. Upon being alerted to this issue, our team took action to minimize impact and restore full service to the small number of impacted sites a as soon as possible. We apologize for any inconvenience that this issue caused, and appreciate your patience and understanding while we worked to resolve it.
Resolved
lovable.dev is back up.
Resolved
Between 14:36 and 14:43 UTC, all GitBook documentation sites using a custom domain were returning a 404 "Not Found" error, making documentation unavailable to users. The issue was caused by a problem introduced by an upstream provider that affected our deployment. The incident was resolved by rolling back the deployment, after which all sites were confirmed to be fully operational.
Resolved
From 13:51 - 13:54 UTC, the Helpdesk had increased errors and latency. Please reach out to team@intercom.io if you experience any issues
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident is now resolved.
Resolved
We have resolved the issue that was preventing users from viewing their active cards in the web page. Cards are now displaying correctly for all users. We apologize for the inconvenience caused.
Resolved
This incident has now been mitigated and services are back to normal.
Resolved
Between 4:53 UTC ending 5:38 UTC, Qwen 3 235B endpoint experienced a partial service disruption due to a transient network issue. The issue has been identified and fixed, the endpoint is operational.
Resolved
This incident has been resolved.
Resolved
k-ID age verification is operating normally again in the UK and Australia. Previously age verified users were not impacted.
Resolved
All background jobs generated by earlier incidents affecting external integrations have now been processed, and system performance has returned to normal. If you’re still experiencing any problems, please reach out to support@linear.app. Thank you for your patience while we worked to resolve this.
Resolved
This incident has been resolved.
Resolved