Live  /  Semgrep  /  Incident

Semgrep: Workflows Performance Degraded

Semgrep · semgrep.devResolved2026-11-03 19:54 UTC
Public — what happened

Summary

Semgrep reported a problem with its Workflows feature, saying that agentic workflows were either not starting or were failing soon after they began. The company said it began looking into this at 18:24 UTC on 2026-11-03, and one minute later it said it had found the issue and was working on a fix. The incident was marked resolved at 19:54, and Semgrep did not describe a cause in its posted updates.

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 46, 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.