Semgrep incident

Investigating issues with pull request checks and repository scans

Major Resolved View vendor source →
Started
Mar 06, 2026, 12:04 PM UTC
Resolved
Mar 06, 2026, 04:18 PM UTC
Duration
4h 14m
Detected by Pingoru
Mar 06, 2026, 12:04 PM UTC

Affected components

GitHub Pull RequestsScans and CI/CDManaged Scans

Update timeline

  1. investigating Mar 06, 2026, 12:04 PM UTC

    We are investigating reports of issues affecting repository scans and pull request checks. Some customers may see scans not starting or checks not appearing on pull requests. We are investigating and will share updates as more information becomes available.

  2. investigating Mar 06, 2026, 12:24 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 06, 2026, 03:47 PM UTC

    We've identified the root cause of the issue that was affecting repository scans and pull request checks, and a fix has now been rolled out. We are now monitoring the results to make sure everything is running smoothly.

  4. resolved Mar 06, 2026, 04:18 PM UTC

    This issue has been resolved, and scans have returned to normal operation.

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