Semgrep incident

Scans failing to start

Resolved after 21 minutes, affecting Scans and CI/CD and Managed Scans, on April 22, 2026.

monitoring Apr 22, 2026, 06:14 PM UTC

We have identified a problem in the service that generates the configuration for new scans. This incident began at approximately 17:30 UTC, and it affects both Managed Scans and CI scans. We have taken action and are actively monitoring the system. If you have a scan that is pending, you can push a new commit to cause the scan to retry.

Started
Apr 22, 2026, 06:14 PM UTC
Resolved
Apr 22, 2026, 06:35 PM UTC
Duration
21m
Detected by Pingoru
Apr 22, 2026, 06:14 PM UTC

Affected components

Scans and CI/CDManaged Scans

Update timeline

  1. monitoring Apr 22, 2026, 06:14 PM UTC

    We have identified a problem in the service that generates the configuration for new scans. This incident began at approximately 17:30 UTC, and it affects both Managed Scans and CI scans. We have taken action and are actively monitoring the system. If you have a scan that is pending, you can push a new commit to cause the scan to retry.

  2. resolved Apr 22, 2026, 06:35 PM UTC

    This incident has been resolved.

Your product runs on more than Semgrep

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →