# Semgrep in January 2026: incidents, uptime and changes

> Semgrep in January 2026: 5 incidents on its status page (2 major or critical), 98.74% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Semgrep’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/semgrep/2026/01
Last updated: 2026-02-01T00:00:00Z

- Incidents posted: 5 (major/critical: 2) · Maintenance: 0
- By vendor impact label: major 2, minor 3
- Uptime (vendor-reported): 98.74% free of major/critical incidents, 95.18% free of any incident; outage time 9 h 22 min, incident time 35 h 50 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [December 2025](https://rewindex.com/company/semgrep/2025/12.md) · Next: [February 2026](https://rewindex.com/company/semgrep/2026/02.md) · [All months](https://rewindex.com/company/semgrep/reports.md) · [Semgrep](https://rewindex.com/company/semgrep.md)

_Uptime: Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Some CI Scans are not completing successfully](https://rewindex.com/company/semgrep/incidents/3bfkp6k0l8zt.md) | major | 2026-01-08 10:40 UTC | 2026-01-08 13:36 UTC | 2.9 h | resolved |
| [Degraded scan performance in CI and Semgrep Managed Scans](https://rewindex.com/company/semgrep/incidents/rmylqm1z4hwr.md) | major | 2026-01-09 17:02 UTC | 2026-01-09 23:27 UTC | 6.4 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Some CI Scans are not completing successfully](https://rewindex.com/company/semgrep/incidents/3bfkp6k0l8zt.md) | major | 2026-01-08 10:40 UTC | 2026-01-08 13:36 UTC | 2.9 h | resolved |
| [Degraded scan performance in CI and Semgrep Managed Scans](https://rewindex.com/company/semgrep/incidents/rmylqm1z4hwr.md) | major | 2026-01-09 17:02 UTC | 2026-01-09 23:27 UTC | 6.4 h | resolved |
| [Issues with starting and completing scans](https://rewindex.com/company/semgrep/incidents/b3f3rm249tb6.md) | minor | 2026-01-13 18:38 UTC | 2026-01-13 15:30 UTC | -188 min | resolved |
| [Intermittent errors in the Semgrep AppSec Platform on some services](https://rewindex.com/company/semgrep/incidents/xnmqcw9kfml1.md) | minor | 2026-01-15 19:47 UTC | 2026-01-16 20:47 UTC | 25 h | resolved |
| [Some managed scans are delayed](https://rewindex.com/company/semgrep/incidents/cdbyvjyy133h.md) | minor | 2026-01-27 23:20 UTC | 2026-01-28 00:47 UTC | 1.4 h | resolved |

## Cite this

Semgrep posted 5 status incidents in January 2026 (2 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/semgrep/2026/01
- Citation: Semgrep, “Semgrep in January 2026” (2026-01-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/semgrep/2026/01 (CC BY 4.0).
- Markdown link: `[Semgrep: Semgrep in January 2026 (2026-01-01)](https://rewindex.com/company/semgrep/2026/01)`


---
Canonical: https://rewindex.com/company/semgrep/2026/01 · Markdown: https://rewindex.com/company/semgrep/2026/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T16:15:32.647Z