Live  /  Semgrep  /  Incident

Semgrep: Dashboard reporting data is lagged

Semgrep · semgrep.devMinor incidentResolved2026-11-11 20:36 UTC
Public — what happened

Summary

Semgrep reported a minor issue in which the data shown on its reporting dashboard was running behind by as much as 18 hours. The company said it had identified the problem at 14:23 UTC on 2026-11-11 and was working through the backlog. Later updates said the delay had shrunk to 7.5 hours and then to under 2 hours, with a return to real-time data expected soon after. Semgrep marked the incident resolved at 20:36 UTC the same day.

Affected

Dashboard

As listed on Semgrep’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the Semgrep status & history page.

Related: Semgrep status & history. SquidGrid is not affiliated with Semgrep.