SnykGitHub Integration Degradation
Snyk engineers have confirmed service recovery. The incident is now resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Snyk engineers have confirmed service recovery. The incident is now resolved.
Resolved
The github incident has been resolved
Resolved
This incident has been resolved and the affected services have been restored.
Resolved
GitHub's APIs appear to be operating normally.
Resolved
We have resolved the issue. Services are back to normal
Resolved
The incident has been resolved
Resolved
We're no longer seeing degradation when interacting with GitHub.
Resolved
This incident has been resolved.
Resolved
On August 13th, 2026, at approximately 18:15 UTC, Akamai observed a brief service outage affecting [_api.linode.com_](http://api.linode.com). The total service interruption lasted for approximately 3 minutes, concluding at 18:18 UTC. Following the restoration of initial connectivity, elevated API response latency persisted through 19:06 UTC, causing slower response times and intermittent delays for customers interacting with API services. To address the performance impact, Akamai engineering teams identified a configuration discrepancy on the secondary caching infrastructure node that prevented it from absorbing the full traffic load after the failover. Engineers completed a controlled migration and moved request caching traffic back over to the primary host. Following this change, API latency rapidly decreased to normal operational levels. The initial condition was triggered by an unexpected reboot of the primary caching node's physical host. While redundant infrastructure was active, the secondary node was unable to process the failover traffic seamlessly, causing the extended performance degradation. Our engineering teams are conducting a follow-up investigation into the failover mechanisms to optimize execution speeds and align configuration settings across redundant nodes, ensuring secondary systems can handle traffic seamlessly in future events. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
This issue has been resolved. New CDC pipes for Postgres are provisioning normally.
Resolved
### Summary An issue with the image registry which powers our hosted agents offering temporarily caused new hosted agent builds in US East to fail. Existing agent workloads were not affected, and no sessions or calls were impacted. ### Timeline \(UTC\) * 19:54 - Hosted agent builds begin failing in US East * 20:48 - Our team noticed the increased failure rate and began investigating * 21:04 - First mitigation deployed * 21:08 - Most builds succeeding * 22:14 - Second mitigation deployed, covering the remaining affected infrastructure * 22:24 - All builds succeeding ### Scope of Impact Only new hosted agent builds and deploys in US East were affected. Agents already running were unaffected, as were all sessions, calls, and other regions. Customers who were impacted would have seen their deploy fail with “unable to deploy agent: an error occurred while building your agent, please try again”. ### Mitigations and Follow-ups * We are improving alerting on build failures. * We are improving monitoring of our downstream image registries. We appreciate your understanding and are committed to continuously improving our platform's reliability. If you have any questions, please reach out to our support team.
Resolved
Logins should be operational again.
Resolved
This incident has been resolved.
Resolved
This issue is resolved.
Resolved
This incident has been resolved.
Resolved
The capacity issue in the ARN region has been resolved.
Resolved
This incident has been resolved.
Resolved
Cloud tasks are now recovering and creation is healthy.
Resolved
All deletion queues have been processed for projects, we expect the same to continue for group deletions. This incident is moved to resolved. More information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22714
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
There have been no further problems, and the incident has been resolved.
Resolved
The issue has been resolved.
Resolved
The incident is resolved
Resolved
The microsoft-multilingual-e5-large model has been retired from the Elastic Inference Service. Requests to this model now return an error. Customers who wish to use this model with Elastic cloud must create a custom inference endpoint using their own API key. See our inference documentation for further details: https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-inference
Resolved
This incident has been resolved. Blueprint management services for US customers are fully operational, and no further impact is expected. We apologize for any inconvenience this may have caused and thank you for your patience.
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
Some customers experienced intermittent Studio connectivity issues between approximately 07:25 and 07:45 UTC on August 17. The issue has been resolved and services have returned to normal operation.
Resolved
We are no longer seeing issues with Logs Alerting and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with Microsoft Azure Metrics Collection and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with CSE Processing Pipeline and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with Metrics Searches and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with CSE Processing Pipeline and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with CSE Processing Pipeline and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with Billing and Account Management and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with CSE Processing Pipeline and normal operation has been restored at this time.
Resolved