Live  /  Providers  /  Semgrep

Semgrep

semgrep.devNo open incidents

Independent assessment — SquidGrid is not affiliated with Semgrep. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

Security & identity · SquidGrid tracks Semgrep’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Semgrep is reporting

Current & recent incidents

Resolved

Dashboard reporting data is lagged

Minor impact · 2026-11-11 20:36 UTC · source

Resolved

Possibly Delayed Scans

Minor impact · 2026-11-07 00:53 UTC · source

Resolved

Workflows Performance Degraded

None impact · 2026-11-03 19:54 UTC · source

Resolved

Scans are degraded or delayed

Minor impact · 2026-10-28 21:39 UTC · source

Resolved

Observed lag in async tasks

Minor impact · 2026-10-15 20:35 UTC · source

Resolved

Intermittent login failures on semgrep.dev

Major impact · 2026-10-05 16:14 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 14 incidents from Semgrep’s own status page since 2026-09-01.

Recent incidents in the archive

Computed by SquidGrid from the incidents Semgrep published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what Semgrep has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Semgrep runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Semgrep is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Semgrep.