Semgrep Status

Resolved: This incident has been resolved.

Monitoring: Dependency processing has resumed and the underlying issue has been resolved.

Identified: We've temporarily disabled dependency processing in order to roll out a longer-term fix. New dependencies will not appear in Semgrep during this time. We don't anticipate any impact to scans, and we'll update this page when normal processing resumes.

Identified: Dependency processing has resumed for scans running now. We're continuing to work on a longer-term mitigation.

Identified: Dependencies found in Supply Chain scans are currently not being processed and recorded. We've identified the cause and are working on a fix. Scan completion is not affected. Dependencies may be temporarily missing from the Semgrep platform; once the incident is resolved and the project is re-scanned, they will be restored.

Resolved: This problem has been resolved. The app is loading normally.

Monitoring: We've released a fix for this problem, and projects and issues should be loading normally. We are monitoring to ensure system stability.

Identified: We are continuing to work on a fix for this issue.

Identified: We've identified a problem with loading issues in the platform. It is not affecting all users, but some users are not currently able to load issues or projects. We are working on a fix.

Resolved: This incident has been resolved.

Identified: We have identified an issue with loading the semgrep.dev website due to an outage with an upstream provider. Users will experience 504 Gateway Timeout errors until this provider outage is resolved.

The Semgrep AppSec Platform is not impacted, but users that rely on navigating to semgrep.dev in order to log in to the platform will be unable to do so. As a workaround, please navigate directly to semgrep.dev/login in the meantime.