All Systems Operational
Platform Success Rate (US - Multi Tenant)
Fetching
Past Incidents
Mar 19, 2024

No incidents reported today.

Mar 18, 2024
Resolved - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced.
Mar 18, 20:05 UTC
Monitoring - The Snyk Incident Response process remains in flight. Mitigation steps have been taken, services have stabilized, and are now under close monitoring.
Mar 18, 17:55 UTC
Investigating - Snyk Monitoring systems have identified that Gitlab PR checks are currently degraded. Other Gitlab features and PR checks from other sources are unaffected.

The Snyk Incident Response process has been invoked. Technical Teams have been engaged and initial triage is underway.

Mar 18, 16:45 UTC
Resolved - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced.
Mar 18, 17:40 UTC
Monitoring - The Snyk Incident Response process remains in flight. Mitigation steps have been taken, services have stabilized, and are now under close monitoring.
Mar 18, 17:38 UTC
Investigating - Snyk monitoring tools have identified an intermittent outage affecting the Snyk platform in Multi-Tenant-US. Snyk Technical Teams are investigating. Additional updates will follow.
Mar 18, 17:25 UTC
Resolved - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced.
Mar 18, 15:26 UTC
Monitoring - Snyk continues to observe delays which are affecting recurring tests. A small percentage of customers are experiencing missed daily test runs, impacting a small number of their projects. Any projects that miss their daily test runs, will complete the run the following day.

Snyk Engineers are aware of the situation and continue to take steps towards mitigating the delays.

Mar 1, 16:19 UTC
Identified - Snyk Technical Teams have observed delays affecting recurring tests. A small percentage of customers is experiencing for a small set of their projects to miss the daily test runs. They will complete the following day instead. Snyk Teams are aware of this situation and are taking steps to mitigate the delay.
Feb 28, 20:50 UTC
Resolved - Snyk Engineers have implemented a fix to fully restore automated tests.
Mar 18, 13:41 UTC
Monitoring - Snyk Engineers have identified that automated testing within the multi-tenant EU environment are being processed at a reduced rate.

A fix for this will be implemented by Monday the 18th of March, until then we expect some level of degradation to affect automated testing.

Mar 13, 17:16 UTC
Mar 17, 2024

No incidents reported.

Mar 16, 2024
Completed - The scheduled maintenance has been completed.
Mar 16, 15:35 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 16, 12:00 UTC
Scheduled - As previously announced, we have a planned maintenance on March 16th. This maintenance period is being reduced to 2 hours from the previously announced 12 hour window. The new maintenance window will be 12 pm UTC to 2 PM UTC.

Maintenance is currently scheduled to take place:

Saturday, March 16th, 12 pm UTC (8 AM ET, 1 PM GMT) to 2 pm UTC (10 AM ET, 3 PM GMT)

We will provide prompt updates on this page if the above date or time changes.

During this period, you may not be able to access Snyk’s services, including the CLI, API, UI and PR checks. For more information on this please check out our Maintenance Guide.

We understand that our services are important to your business operations and we have designed our maintenance process to minimize inconvenience to our customers. This maintenance window enables us to upgrade the Snyk platform to our new, more robust, and reliable service architecture, to better meet your business needs and to continue to scale in the future.

We will provide status updates during the maintenance window at status.snyk.io. If you have any questions or need any assistance, please don't hesitate to contact our support team.

Mar 13, 01:45 UTC
Mar 15, 2024
Resolved - The Snyk Incident Response process has been stood down. All services have been restored, and no impact is currently being experienced.
Mar 15, 18:56 UTC
Monitoring - The Snyk Incident Response process remains in flight. Snyk Technical Teams have taken action to mitigate the incident. Services are now restored and are under close monitoring conditions.
Mar 15, 18:42 UTC
Investigating - Snyk monitoring services have identified the Cloud Compliance Report as unresponsive. The Snyk Incident Response process has been evoked. Technical Teams have been engaged. Initial triage is underway.
Mar 15, 18:13 UTC
Mar 14, 2024

No incidents reported.

Mar 13, 2024
Resolved - Snyk Engineers identified a degradation in service from 09:30 UTC to 09:45 UTC due to higher than expected load.

Snyk Engineers have increased the resources available to handle this in future. Services have fully recovered and no further impact is expected.

Mar 13, 13:37 UTC
Monitoring - Snyk Monitoring tools identified a brief outage which affected the Snyk platform at approximately 09:30 UTC. Services have now recovered.

Snyk Engineers continue to investigate the cause of the outage.

Mar 13, 10:04 UTC
Identified - Snyk Monitoring tools have identified a brief outage which affected the Snyk platform at approximately 09:30 UTC. Services have now recovered.

Snyk Engineers are investigating the cause of the outage.

Mar 13, 09:57 UTC
Mar 12, 2024

No incidents reported.

Mar 11, 2024

No incidents reported.

Mar 10, 2024

No incidents reported.

Mar 9, 2024

No incidents reported.

Mar 8, 2024

No incidents reported.

Mar 7, 2024
Resolved - Snyk Technical Teams have mitigated the issue and have confirmed Project Move API is working as intended. The Incident Response has been stood down as this Incident is now Resolved.
Mar 7, 17:05 UTC
Identified - Snyk Technical Teams are investigating failures observed with the Project Move API. Customers may receive a 500 response when using the Project Move API. The Snyk Incident Response has been enacted. Snyk Technical Teams have identified the issue and are taking corrective actions; additional updates will follow.
Mar 7, 15:34 UTC
Resolved - The Snyk platform experienced a brief outage which affected 0.3% of traffic between 11:08:50 and 11:09:00 UTC.

This has been revised from the original impact statement where it was believed that there was a partial platform outage between 11:07 and 11:09 UTC.

Snyk Engineers have confirmed all services have been restored.

Mar 7, 11:38 UTC
Resolved - Snyk Engineers have implemented a fix to restore IaC+ scanning.

SCM scans were impacted between 16:30 UTC (6th March) and 10:20 UTC today.

Cloud scans were impacted between 16:30 UTC (6th March) and 11:08 UTC today.

Customers will need to re-import repositories and re-onboard cloud environments that were initially attempted during the above outage windows. Any failed recurring tests will be run during the next schedule.

This incident did not affect the standard Snyk IaC offering.

Mar 7, 11:26 UTC
Identified - Snyk Monitoring systems have identified that IAC+ scans are currently degraded. Customers may observe issues when attempting Cloud Scans.

There was limited impact to SCM scans which has now been resolved.

This does not affect the standard Snyk IaC offering.

Mar 7, 10:27 UTC
Mar 6, 2024
Resolved - Snyk are no longer observing delays in Reporting data.

The Snyk incident response has now been stood down.

Mar 6, 14:47 UTC
Monitoring - Snyk continues to observe a delay which is impacting Reporting data for a small percentage of projects. However, the underlying cause of the delay has been identified and data is now backfilling at an increased rate.

Snyk Engineers are aware of the situation and continue to take steps towards mitigating the delays.

Mar 6, 09:28 UTC
Investigating - Snyk Monitoring tools have identified a significant delay which is currently impacting Reporting for a small percentage of projects.

Snyk Engineers have commenced troubleshooting the issue.

The Snyk incident response has been invoked.

Mar 5, 11:40 UTC
Mar 5, 2024