Snyk incident: PR Checks Degraded

Affected components

• Snyk Open Source

1. resolvedMay 22, 2026, 19:14 UTC

   Snyk engineers have rolled out a fix across all environments. Our engineers will continue to monitor the situation. The Snyk Incident Response has been stood down.

2. identifiedMay 22, 2026, 17:26 UTC

   Snyk engineers have identified the root cause of degraded performance affecting Open Source across all environments, leading to PR Checks and recurring test failures. A fix is currently being rolled out globally. We will provide further updates as the deployment progresses.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Twilio: Subset of AU Sender ID Registration Submissions Directly Transitioning to REJECTEDMinor · May 15, 2026, 20:51 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Twilio: SMS Delivery Delays From Twilio to Multiple Networks in Multiple Countries in EuropeMinor · May 19, 2026, 13:21 UTC
• Twilio: SMS Delivery Failures from Network Subscribers to Twilio Denmark Phone NumbersMinor · May 20, 2026, 07:58 UTC
• Twilio: SMS Delivery Receipt Delays From a Subset of Twilio Long Codes and Toll-Free Numbers to Viaero United StatesMinor · May 21, 2026, 22:59 UTC
• Linode: Service Issue - Paris (FR-PAR3)Minor · May 22, 2026, 11:22 UTC
• OVHcloud: [GRA/RBX/DE][Storage and Backups] - Object Storage Incident NotificationMinor · May 22, 2026, 15:04 UTC
• Clerk: Issue with Provisioning DomainsMinor · May 22, 2026, 15:48 UTC
• Calendly: Error on Meetings pageMinor · May 22, 2026, 17:01 UTC

How often does Snyk have incidents?

Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history