Live / Incidents / Semgrep
Semgrep: Backend 503 timeout on all pages
Semgrep · semgrep.devImpact: noneResolved2026-09-30 18:23 UTC
Public — what happened
Summary
Monitoring indicates the platform continues to be stable, and this issue has been resolved.
Timeline
- Started — 2026-09-30 14:07 UTC
- Last update — 2026-09-30 18:23 UTC
- Resolved — 2026-09-30 18:23 UTC
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 →