Elevated git clone duration at build time

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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`

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`

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`

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`

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`

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`

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`

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`

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`

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`

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`

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`

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

We have mitigated the impact of the underlying issue by moving builds from pdx1 to iad1 while we continue to investigate the underlying cause.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

The new build routing has addressed the issue. We are monitoring the results.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.