Live / Semgrep / Incident
Semgrep: Observed lag in async tasks
Semgrep · semgrep.devMinor incidentResolved2026-10-15 20:35 UTC
Public — what happened
Summary
Semgrep reported on October 15, 2026 at 19:18 UTC that it was looking into delays affecting some background tasks that run asynchronously on its platform, an issue it classified as minor. The company did not say which customers were affected or share a cause. The incident was marked resolved at 20:35 the same day.
Affected
Dashboard, API
Timeline
- Started — 2026-10-15 19:18 UTC
- Investigating — 2026-10-15 19:18 UTC
- Resolved — 2026-10-15 20:35 UTC · 1h 18m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Semgrep against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Semgrep: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Semgrep report →
More from Semgrep
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.