# Vercel in January 2026: incidents, uptime and changes

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

Canonical: https://rewindex.com/company/vercel/2026/01
Last updated: 2026-06-17T09:46:13Z

- Incidents posted: 5 (major/critical: 1) · Maintenance: 0
- By vendor impact label: major 1, minor 4
- Uptime (vendor-reported): 98.37% free of major/critical incidents, 94.85% free of any incident; outage time 12 h 5 min, incident time 38 h 15 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 2
- Previous month: [December 2025](https://rewindex.com/company/vercel/2025/12.md) · Next: [February 2026](https://rewindex.com/company/vercel/2026/02.md) · [All months](https://rewindex.com/company/vercel/reports.md) · [Vercel](https://rewindex.com/company/vercel.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 |
| --- | --- | --- | --- | --- | --- |
| [Elevated build failure rates](https://rewindex.com/company/vercel/incidents/x6v2pmf14f75.md) | major | 2026-01-13 22:45 UTC | 2026-01-14 10:50 UTC | 12 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Elevated build failure rates](https://rewindex.com/company/vercel/incidents/x6v2pmf14f75.md) | major | 2026-01-13 22:45 UTC | 2026-01-14 10:50 UTC | 12 h | resolved |
| [Some domain purchases are failing](https://rewindex.com/company/vercel/incidents/7kjxsr1slq31.md) | minor | 2026-01-23 03:35 UTC | 2026-01-23 04:28 UTC | 53 min | resolved |
| [Delayed Dashboard Data Across Multiple Services](https://rewindex.com/company/vercel/incidents/262wldl871w4.md) | minor | 2026-01-26 14:50 UTC | 2026-01-26 17:57 UTC | 3.1 h | resolved |
| [Elevated Connection Latency in dub1 (Dublin, Ireland) Edge Region](https://rewindex.com/company/vercel/incidents/xdv869lr3x7n.md) | minor | 2026-01-28 17:19 UTC | 2026-01-28 20:21 UTC | 3.0 h | resolved |
| [Elevated git clone duration at build time](https://rewindex.com/company/vercel/incidents/ycfd8q0x22zy.md) | minor | 2026-01-29 16:00 UTC | 2026-01-30 11:08 UTC | 19 h | resolved |

## CVEs published

- [CVE-2025-59471](https://rewindex.com/cve/CVE-2025-59471.md)  (CVSS 5.9), published 2026-01-26
- [CVE-2025-59472](https://rewindex.com/cve/CVE-2025-59472.md)  (CVSS 5.9), published 2026-01-26

## Cite this

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

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


---
Canonical: https://rewindex.com/company/vercel/2026/01 · Markdown: https://rewindex.com/company/vercel/2026/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T15:56:39.963Z