Incident history
May 28, 2026
This incident has been resolved.
May 28, 2026 · 16:00 → 16:59May 27, 2026
This incident has been resolved. We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC.
May 27, 2026 · 04:50 → 05:02May 25, 2026
This incident has been resolved.
May 25, 2026 · 14:58 → 16:22May 23, 2026
This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt
May 23, 2026 · 10:43 → 18:44May 22, 2026
Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deploymen
May 22, 2026 · 17:11 → 17:11May 21, 2026
This incident has been resolved.
May 21, 2026 · 15:01 → 21:31May 20, 2026
This incident has been resolved. Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up as we back
May 20, 2026 · 20:07 → 06:08May 18, 2026
This incident has been resolved. Some deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments cr
May 18, 2026 · 21:42 → 23:52The incident is resolved and support cases can be submitted again.
May 18, 2026 · 15:00 → 15:41