Live  /  Semgrep  /  Incident

Semgrep: General issues with application loading, scan processing, and results processing.

Semgrep · semgrep.devResolved2026-11-12 18:47 UTC
Public — what happened

Summary

Semgrep said that starting at 17:08 UTC on 2026-11-12 it was dealing with slowdowns affecting how quickly its application loaded and how fast scans and their results were processed. By 17:35 UTC the company said it had found the underlying problem and was working on a remedy. It reported putting a fix in place and seeing early recovery at 17:48 UTC, then said at 18:00 UTC it was watching systems as they kept recovering. The incident was marked resolved at 18:47 UTC.

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.