BuildKiteIncreased dispatch latency and error rates
Previously elevated loads with Hosted Agents dispatch have fully recovered.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Previously elevated loads with Hosted Agents dispatch have fully recovered.
Resolved
The Amplitude web application in the US was briefly inaccessible. We identified the issue to be related to a misconfigured feature flag. The issue started at 10:00 AM PST, lasting 10 minutes, and is now resolved.
Resolved
On April 22, 2026 from 18:49 to 19:32 UTC , the Copilot Cloud Agent service began failing during session execution for users running the Agent HQ Codex agent. Codex agent sessions failed to start for all entry points (issue assignment, @copilot comment mentions). 0.5% of total Copilot Cloud Agent jobs were impacted (~2,000 failed jobs). Copilot and other agent sessions were unaffected.<br /><br />This was caused by a model resolution mismatch in Codex agent sessions, resulting in an incompatible model being used at runtime. A mitigation was deployed to select a stable default model for Codex agent sessions.<br /><br />We are working to harden the underlying model-resolution path so it correctly scopes to the requesting agent's supported models to prevent similar failure mode in the future.
Resolved
The system has recovered and functionality has returned to normal.
Resolved
This incident has been resolved.
Resolved
Incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 18:45 and 19:42 UTC on April 23, users were unable to start new agent tasks using either Claude or Codex agent on github.com. This was caused by a code change to how Copilot mission control routes task creation requests. Ongoing agent tasks and other Copilot agent features were not affected. We mitigated the impact by reverting the breaking change. We are adding extra monitoring and integration test coverage for the task creation path to prevent future recurrence.
Resolved
Agent version 3.39.1 is now available in the Microsoft Store.
Resolved
Engineers have released a fix to address the issues impacting the platform. Normal service has been restored for all impacted users.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
Following continued monitoring after mitigation was applied, we can confirm that the issue has been fully resolved and all affected AI-powered functionality is operating normally. We apologize again for the inconvenience caused.
Resolved
Following continued monitoring after mitigation was applied, we can confirm that the issue has been fully resolved and all affected AI-powered functionality is operating normally. We apologize again for the inconvenience caused.
Resolved
Following continued monitoring after mitigation was applied, we can confirm that the issue has been fully resolved and all affected AI-powered functionality is operating normally. We apologize again for the inconvenience caused.
Resolved
This issue has been resolved, and the error message should disappear in a couple of minutes. Thanks for your patience!
Resolved
All systems are operating normally. The issue has been fully resolved and we are continuing to monitor to ensure stability.
Resolved
We identified a configuration issue that caused a small selection of banking providers to be incorrectly enabled or disabled for some clients. As a result, some end-users might have been unable to find their usual provider, or conversely, saw providers that were not previously enabled for your client_id. This issue has now been resolved, and all providers have been rectified back to their original state for your client_id. Impact start time: 13/04/2026, 13:00 UTC Impact end time: 28/04/2026, 13:00 UTC Client actions: None
Resolved
False positive
Resolved
This incident has been resolved. Annotation queues are once again fully accessible in the US LangSmith UI. Please let us know at support@langchain.dev if you're still experiencing issues.
Resolved
This incident has been resolved. Annotation queues are once again fully accessible in the EU LangSmith UI. Please let us know at support@langchain.dev if you're still experiencing issues.
Resolved
This incident has been resolved and dependency scanning is now operational. More information can be found in gitlab.com/gitlab-com/gl-infra/production/-/work_items/21905.
Resolved
The issue has been resolved.
Resolved
This incident has been resolved.
Resolved
Forum is back up
Resolved
This issue has now been resolved and login should be back to normal.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
After monitoring the fix, we can confirm our team has resolved the disruption. We appreciate your patience and understanding with our team today as we worked to address this.
Resolved
We've confirmed the issue is resolved. Thanks for your patience.
Resolved
This incident has been resolved.
Resolved
On April 24, 2026, from approximately 11:39 UTC to April 25, 2026 at 00:15 UTC, GitHub Actions experienced delays and timeouts for Larger Hosted Runner jobs using VNet injection in the East US region without a failover region configured. Standard and Self-hosted runners were not impacted. This was caused by backend failures in our compute provider’s provisioning, scaling, and update operations for VMs in the East US region and mitigated by a rollback across all affected Availability Zones. More detail is available at https://azure.status.microsoft/en-us/status/history/?trackingId=5GP8-W0G.<br /><br />We are working to improve the reliability of our annotations for jobs impacted by regional issues and are adding system log notifications as an additional customer communication channel alongside annotations.<br /><br />VNet Failover is also now in public preview, allowing customers to evacuate Larger Hosted Runners using VNet injection in cases like this.
Resolved
The issue preventing ownership transfer in Teams and Enterprise accounts has been resolved. Account ownership transfers can now be self-served by following this guide: https://help.zapier.com/hc/en-us/articles/17946190203789-How-to-transfer-ownership-of-your-Team-or-Enterprise-account If you're experiencing any issues with this, please do reach out to our support team here: https://zapier.com/app/get-help
Resolved
This is resolved, managed auth health checks have resumed normal operation.
Resolved
On April 21, 2026, between 13:35 UTC and 01:24 UTC the following day the projects service was degraded. During this time period, projects may have been out of sync and users may have experienced delays in changes to projects and their items. Delays in reflected changes peaked at approximately 45 minutes. The delays were caused by serialization errors that failed events and triggered a flood of resyncs, overloading our event processing layers.<br /><br />We mitigated the incident by speeding up processing time for incoming changes and otherwise waiting for all changes to be processed.<br /><br />We are working to increase our capacity for processing updates to projects to reduce our time to mitigation of issues like this one in the future.
Resolved
This incident has been resolved.
Resolved
An issue impacting the Event Triggered Journey user interface in the application has been resolved. Prior to resolution, customers may have experienced an error in the user interface impacting their ability to configure Activations for Event Triggered Journeys.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved and all data is visible.
Resolved