All Systems Operational

SNYK-US-01 (app.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
SNYK-US-02 (app.us.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
SNYK-EU-01 (app.eu.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
SNYK-AU-01 (app.au.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
SNYK-GOV-01 (app.snykgov.io) Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Dec 13, 2025

No incidents reported today.

Dec 12, 2025

No incidents reported.

Dec 11, 2025

No incidents reported.

Dec 10, 2025

No incidents reported.

Dec 9, 2025

No incidents reported.

Dec 8, 2025
Snyk Open Source and Container Degradation
Resolved - Our Engineers have observed no further impact during our monitoring period.

We can confirm that our Snyk Code product would have also experienced degradation as a result of this incident.

The Snyk Incident Response has now been stood down.
Dec 8, 13:51 UTC
Monitoring - Our Engineers have deployed a fix, and initial signs are positive.

We are monitoring to ensure services remain stable.
Dec 8, 13:28 UTC
Identified - We have identified the root cause of the degradation and are working on a fix.

We will keep you updated on our progress.
Dec 8, 13:14 UTC
Update - We are continuing to investigate this issue.
Dec 8, 12:56 UTC
Investigating - Our Engineers are aware of degradation affecting Snyk Open Source and Container products across app.au.snyk.io environment.

Customers will observe that test-related operations, such as imports, manual tests, and manual retests, among others, will be degraded.

The Snyk Incident Response has been invoked, and our investigation is in progress.
Dec 8, 12:53 UTC
Dec 7, 2025

No incidents reported.

Dec 6, 2025

No incidents reported.

Dec 5, 2025

No incidents reported.

Dec 4, 2025

No incidents reported.

Dec 3, 2025

No incidents reported.

Dec 2, 2025
Errors When Using Broker Image 5.3.0
Resolved - The Snyk Incident response has been stood down. This incident is now resolved.
Dec 2, 20:45 UTC
Monitoring - Snyk Engineers have released a fix. Customers may upgrade the Broker Client Image 5.3.1, which resolves the errors. Snyk Engineers are monitoring at this time.
Dec 2, 19:57 UTC
Identified - Customers who have upgraded the Broker image to 5.3.0 are facing the following error:

Error [ERR_MODULE_NOT_FOUND]:

Snyk Engineers are aware of the issue and are taking steps to mitigate under an incident footing.
Customers are encouraged to revert to Broker Image 5.2.0 while migration is ongoing.
Dec 2, 19:50 UTC
Dec 1, 2025

No incidents reported.

Nov 30, 2025

No incidents reported.

Nov 29, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage