Search

Companies / Semgrep / incidents

Semgrep: Failure to start scans from 14:35 to 14:52 UTC

Impact: majorStatus: resolvedStarted Resolved (-247 min)1 updateSource: stspg.io (opens in new tab)
Summary

Semgrep reported a major outage: scans failed to start from 14:35 to 14:52 UTC. The vendor said it mitigated the issue and scans were starting normally. The incident is marked resolved, but its recorded start (2026-04-24 16:37 UTC) and resolution (2026-04-24 12:30 UTC) conflict; computed duration is unknown.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Timeline of updates

  1. resolved

    From 14:35 to 14:52 UTC, Semgrep scans did not start successfully. We have mitigated the issue and scans are now starting normally.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Semgrep profile · Recent Semgrep incidents · Markdown · JSON