# Semgrep in January 2025: incidents, uptime and changes

> Semgrep in January 2025: 3 incidents on its status page (2 major or critical), 99.93% 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/2025/01
Last updated: 2025-02-01T00:00:00Z

- Incidents posted: 3 (major/critical: 2) · Maintenance: 0
- By vendor impact label: major 2, minor 1
- Uptime (vendor-reported): 99.93% free of major/critical incidents, 99.36% free of any incident; outage time 30 min, incident time 4 h 43 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [December 2024](https://rewindex.com/company/semgrep/2024/12.md) · Next: [February 2025](https://rewindex.com/company/semgrep/2025/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 |
| --- | --- | --- | --- | --- | --- |
| [GitHub Outage Impacting Semgrep Managed Scanning](https://rewindex.com/company/semgrep/incidents/jv2zd9fn1s59.md) | major | 2025-01-14 00:05 UTC | 2025-01-14 00:35 UTC | 30 min | resolved |
| [Supply chain dependency and license processing degraded](https://rewindex.com/company/semgrep/incidents/zldjy7s20kn7.md) | major | 2025-01-16 16:30 UTC | 2025-01-16 16:30 UTC | 0 min | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [GitHub Outage Impacting Semgrep Managed Scanning](https://rewindex.com/company/semgrep/incidents/jv2zd9fn1s59.md) | major | 2025-01-14 00:05 UTC | 2025-01-14 00:35 UTC | 30 min | resolved |
| [SMS scanning is degraded](https://rewindex.com/company/semgrep/incidents/5bntt53z8fm2.md) | minor | 2025-01-14 22:21 UTC | 2025-01-15 02:34 UTC | 4.2 h | resolved |
| [Supply chain dependency and license processing degraded](https://rewindex.com/company/semgrep/incidents/zldjy7s20kn7.md) | major | 2025-01-16 16:30 UTC | 2025-01-16 16:30 UTC | 0 min | resolved |

## Cite this

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

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


---
Canonical: https://rewindex.com/company/semgrep/2025/01 · Markdown: https://rewindex.com/company/semgrep/2025/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:51:18.879Z