Semgrep incident

Scans failing to start

Critical Resolved View vendor source →
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.

Looking to track Semgrep downtime and outages?

Pingoru polls Semgrep's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Semgrep reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Semgrep alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Semgrep for free

5 free monitors · No credit card required