🟢 Operational
Increased build and deployment failures
Resolved
- Started
- 2026-10-12 13:35 UTC
25 days ago - Last update
- 2026-10-12 20:11 UTC
25 days ago - Duration
- 6h 36m
Timeline
-
12 Oct · 20:11 UTC
🟠 Resolved
atom
Oct 12, 20:11 UTC
Resolved - This incident has been resolved.
Oct 12, 19:56 UTC
Monitoring - The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
Oct 12, 18:33 UTC
Update - Deployment events, such as updating the deployment status on pull requests, are delayed and the backlog is being processed. We will provide additional updates as they become available.
Oct 12, 16:10 UTC
Update - We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available.
Oct 12, 14:57 UTC
Update - Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.
Oct 12, 14:08 UTC
Identified - We have identified the issue and are working on a fix. We will provide additional updates as they become available.
Oct 12, 13:35 UTC
Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available. -
12 Oct · 19:56 UTC
🟠 Monitoring
atom
Oct 12, 19:56 UTC
Monitoring - The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.
Oct 12, 18:33 UTC
Update - Deployment events, such as updating the deployment status on pull requests, are delayed and the backlog is being processed. We will provide additional updates as they become available.
Oct 12, 16:10 UTC
Update - We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available.
Oct 12, 14:57 UTC
Update - Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.
Oct 12, 14:08 UTC
Identified - We have identified the issue and are working on a fix. We will provide additional updates as they become available.
Oct 12, 13:35 UTC
Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available. -
12 Oct · 18:33 UTC
🟠 Identified
atom
Oct 12, 18:33 UTC
Update - Deployment events, such as updating the deployment status on pull requests, are delayed and the backlog is being processed. We will provide additional updates as they become available.
Oct 12, 16:10 UTC
Update - We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available.
Oct 12, 14:57 UTC
Update - Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.
Oct 12, 14:08 UTC
Identified - We have identified the issue and are working on a fix. We will provide additional updates as they become available.
Oct 12, 13:35 UTC
Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available. -
12 Oct · 16:11 UTC
🟠 Identified
atom
Oct 12, 16:10 UTC
Update - We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available.
Oct 12, 14:57 UTC
Update - Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.
Oct 12, 14:08 UTC
Identified - We have identified the issue and are working on a fix. We will provide additional updates as they become available.
Oct 12, 13:35 UTC
Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available. -
12 Oct · 16:10 UTC
🟠 Identified
atom
Oct 12, 16:10 UTC
Update - [6:10 PM]We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available.
Oct 12, 14:57 UTC
Update - Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.
Oct 12, 14:08 UTC
Identified - We have identified the issue and are working on a fix. We will provide additional updates as they become available.
Oct 12, 13:35 UTC
Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available. -
12 Oct · 14:57 UTC
🟠 Identified
atom
Oct 12, 14:57 UTC
Update - Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available.
Oct 12, 14:08 UTC
Identified - We have identified the issue and are working on a fix. We will provide additional updates as they become available.
Oct 12, 13:35 UTC
Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available. -
12 Oct · 14:08 UTC
🟠 Identified
atom
Oct 12, 14:08 UTC
Identified - We have identified the issue and are working on a fix. We will provide additional updates as they become available.
Oct 12, 13:35 UTC
Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available. -
12 Oct · 13:35 UTC
🟠 Investigating
atom
Oct 12, 13:35 UTC
Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available.
Source
Official Vercel status — view original incident ↗
IT Status normalizes vendor wording into a common vocabulary and rewrites machine-shaped titles for readability. The vendor's page remains authoritative.