Snyk incident: Partial Broker Service Degradation

Affected components

• Snyk AppRisk
• Snyk Code
• Snyk Container
• Snyk IaC
• Snyk Open Source

1. resolvedAug 30, 2026, 13:31 UTC

   A fix has been applied, and error rates connecting to our broker servers have dropped back to normal levels. Connections via brokered integrations are functioning as expected. We are continuing to monitor performance to ensure full stability.

2. investigatingAug 30, 2026, 12:20 UTC

   Our engineering team has detected an issue impacting customers using brokered integrations. Some customers are currently reporting errors when attempting to connect to our broker servers. At this time, only a subset of customers is affected. We are actively measuring the impact of this service degradation and investigating the root cause. We will provide another update as soon as we have more information.

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.

• Supabase: Increased response times for requestsMajor · Aug 27, 2026, 17:20 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Shippo: Elevated error rate on DHL Express label generationMinor · Aug 28, 2026, 19:39 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