SnykSnyk Open Source .NET Tests Failing
Our engineers have deployed a fix and, after a brief monitoring period, have confirmed all services have recovered. The Snyk Incident Response has been stood down.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Our engineers have deployed a fix and, after a brief monitoring period, have confirmed all services have recovered. The Snyk Incident Response has been stood down.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been fixed and we’re confident it’s resolved SumUp services have returned to normal. You can stay up to date on the status of our services anytime here on our status page: https://status.sumup.com.
Resolved
Our team has been able to identify the issue and deploy a fix quickly.
Resolved
Problem: A brief connectivity issue between our control plane and data plane prevented users from creating or deploying new applications. Impact: For about 15 minutes, users were unable to create or deploy new applications, and stale application states could be shown in the dashboard. Existing applications were not affected. Causes: An uncoordinated rollout of two separate systems caused a brief connectivity issue between our control plane and data plane.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
This issue has been resolved and images should be loading normally on all clients.
Resolved
# Summary On 17 July 2026, following a routine code deployment, customers on older delegate versions \(858xx and below\) began experiencing delayed CI builds on Harness Cloud-hosted builds using our global build-queueing capability. Affected builds experienced an unexpected pause of up to approximately 8 minutes at the "waiting for infrastructure" stage before continuing, rather than proceeding within the expected sub-second time. Overall build slowness was intermittent. # Impact * All CI builds were potentially subject to delay; impact was most pronounced for builds on Harness Cloud-hosted infrastructure using the global build-queueing feature. * Affected builds experienced an unexplained pause of up to approximately 8 minutes before continuing, followed by a slower "cold start" since a pre-reserved compute slot was not available — this presented to users as slow builds rather than build failures. * Accounts running on newer delegate versions \(858xx and above\) were not impacted. * No builds failed outright as a direct result of this issue, and no data was lost. # Root Cause The root cause was an internal code change that inadvertently broke how a specific build-queueing record was read back from our database once builds that had already been queued under the previous version of the code encountered the newly deployed version. We resolved the immediate impact by cleaning up the affected records and reverting the underlying code change, and we are implementing several safeguards to prevent this class of issue from recurring. # Next Steps We assess the risk of a similar recurrence as low as the following actions are being understaken.The specific code path that caused this incident has already been reverted, and we are implementing structural safeguards so that this general class of issue cannot recur, regardless of where in the codebase it might otherwise occur. | **Corrective / Preventive Action** | | --- | | Add explicit, stable identifiers to all internal data classes that get stored in our database, so that future internal code reorganizations cannot break the system's ability to read back previously stored records. | | Introduce rollback and backward-compatibility testing in our pre-production environment, specifically designed to catch this class of issue before it reaches production. |
Resolved
The issue affecting TanStack application previews and published apps has been resolved. All systems are operating normally.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
After a period of monitoring we have seen continued Gitaly stability and consider the incident resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22625.
Resolved
On July 16, 2026, GitHub Copilot users experienced elevated errors when using Claude Fable 5 from 17:33 UTC until mitigation at 22:04 UTC. The average error rate was 1.4%, with a maximum error rate of 30.85%. The issue was caused by degradation at an upstream model provider; other Copilot models were not significantly affected, and users could avoid the impact by selecting another model or Auto. Service recovered after the provider mitigated the degradation.
Resolved
This incident has been resolved.
Resolved
This issue was resolved on Friday, July 31, at approximately 3:00 PM CST.
Resolved
We have resolved an issue where customers were unable to programmatically install the Vanta agent using our installation scripts (such as deployments via MDM). This was caused by an unexpected permissions change that made the scripts repository private starting on July 31, 2026, at 3:07 PM UTC. Full access has been restored, and scripted installations are now functioning normally. Direct agent installations were unaffected during this time. We apologize for any disruption this may have caused to your deployment processes.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The system has returned to normal operation.
Resolved
The issue has been resolved, and service has returned to normal. We identified the root cause, implemented a mitigation, and have observed stable system performance following the change. We will continue to monitor the service closely to ensure ongoing stability. Thank you for your patience while we worked to resolve this issue.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
The issue has been resolved and service has remained stable following the rollback. We will continue to monitor internally, but this incident is now considered resolved.
Resolved
A Instabilidade na tela de chat e impactos na distribuição de atendimentos no RD Station Conversas foi resolvida com sucesso. Caso você note que sua conta ainda contém alguma inconsistência, por favor, entre em contato com nosso Time de Suporte através da nossa Central de Ajuda "através da nossa Central de Ajuda": http://ajuda.rdstation.com/..
Resolved
Between 13:35 UTC and 15:53 UTC customers experienced degraded search performance in the Inbox. Intermittently during the initial period of the investigation, some customers experienced conversations that failed to load in the Inbox. This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.ai if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
The incident has been resolved.
Resolved
We have fixed the data pipeline delay and all sessions should be loading now in the Cloud Dashboard.
Resolved
This issue is resolved and we're back to regular processing times.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
A BGP misconfiguration while provisioning new edge capacity caused most traffic from Europe endpoints to be dropped, between 14:50 UTC and 15:02 UTC. The misconfiguration has been fixed and we are implementing safeguards against this kind of issue in the future.
Resolved
Between 09:36 and 13:30 UTC on August 3, some customers experienced intermittent errors while accessing the DigitalOcean Cloud Control Panel. We renewed the affected internal certificates and restored access. The issue is resolved, and the Cloud Control Panel is operating normally. We apologize for the disruption.
Resolved
This incident has been resolved.
Resolved
Live chat is working properly, and the incident should be fully resolved.
Resolved
This has been resolved.
Resolved
This incident has been resolved.
Resolved
We have fixed the problem and issued refunds to the affected customers. Please email support if you still believe you are having issues. Once again, we're sorry for any inconvenience caused by this issue.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved