← Back to Vercel History
minor✓ Resolved

Elevated git clone duration at build time

VercelFri, Jan 30, 2026, 02:40 AM
Status
resolved
Duration
8h 29m
Updates
6
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedFri, Jan 30, 2026, 11:10 AM
This incident has been resolved.
monitoringFri, Jan 30, 2026, 10:42 AM
The new build routing has addressed the issue. We are monitoring the results.
investigatingFri, Jan 30, 2026, 10:24 AM
We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.
investigatingFri, Jan 30, 2026, 09:02 AM
We are continuing to investigate this issue.
investigatingFri, Jan 30, 2026, 06:21 AM
We are continuing to investigate this issue.
investigatingFri, Jan 30, 2026, 03:47 AM
We’ve confirmed the issue is intermittent, and redeploying a failed build may succeed. Alternatively, as a temporary workaround, builds can be run locally and deployed as prebuilt output using Vercel CLI: `vercel build && vercel deploy --prebuilt`
investigatingFri, Jan 30, 2026, 02:40 AM
We are currently observing elevated `git clone` durations on a subset of builds. Some builds are taking significantly longer than expected to clone repositories, resulting in slower overall build start times. We are actively analyzing clone performance metrics and infrastructure behavior to identify the root cause.

📊 TECHNICAL DETAILS

Internal ID
e56c6bf5-b926-420b-a1f4-06a63d930156
External ID
ycfd8q0x22zy
🕐 Started
Fri, Jan 30, 2026, 02:40 AM
🔄 Last Updated
Fri, Jan 30, 2026, 11:10 AM
✓ Resolved
Fri, Jan 30, 2026, 11:10 AM
MINOR
Impact Level
8h 29m
Total Duration
6
Status Updates
Affected Components
Git Integrations
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed