Semgrep Outage History

Issue has been identified and a fix is rolling out

We are currently investigating issues with scans uploading findings which prevents the successful completion of scans. Additionally, we are aware of issues accessing the web user interface.

A small number (<1%) of supply chain scans that dynamically resolve dependencies for gradle and maven projects have been failing since August 28, due to rate limiting applied by a public package registry. Affected projects may show incomplete or missing Supply Chain findings. We are rolling out a caching mirror to reduce the impact of these rate limits. Subsequent scheduled scans should resolve any impacted findings. No further action from customers is required at this time.

Under one percent of supply chain scans that dynamically resolve dependencies for gradle and maven projects have been failing, due to rate limiting applied by a third-party package registry. Affected projects may show incomplete or missing Supply Chain findings. We are rolling out a caching mirror to reduce the impact of these rate limits. Subsequent scheduled scans should resolve any impacted findings. No further action from customers is required at this time

A bad release is causing widespread failures in the Semgrep AppSec Platform.

We've identified the root cause of the issue and are currently working on a fix.

We have identified the issue and are actively working on a fix.

We've identified the root cause and observed that both creating and editing memories is affected. We are working on a fix for the issue.

We have observed widespread scan failures relating to a bad release of AI skills rules. We are working to fix the issue. To prevent the issue in the meantime, you can disable the "skills.behavioral.skill-destructive-commands.skill-destructive-commands" rule in your Semgrep policies.

The issue has been identified and a fix is being implemented.

The issue has been identified and a fix is being implemented.

We are currently observing login issues using GitHub auth. Our team has identified the issue and is currently working on a fix. SSO logins are working as expected and are not impacted.

We have identified the issue and are working on a resolution.

We have identified a likely cause of this incident. We are currently rolling out a change to address it.

Since the beginning of the incident, a portion of SMS scans have failed to execute. We have deployed a change to the system. We are seeing scheduling queues begin to recover, and we're continuing to monitor the situation.

The issue has been identified and a fix is being implemented.