Changes / Semgrep / Failure to start scans from 14:35 to 14:52 UTC
Semgrep: Major incident: Failure to start scans from 14:35 to 14:52 UTC
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 diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Failure to start scans from 14:35 to 14:52 UTC
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-24 16:37 UTC
Before: not present
After: 2026-04-24 12:30 UTC
Before: not present
After: From 14:35 to 14:52 UTC, Semgrep scans did not start successfully. We have mitigated the issue and scans are now starting normally.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Failure to start scans from 14:35 to 14:52 UTC (this change) 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. | Major incident |