🟢 Operational
Build failures and 500 errors for functions using Edge runtime
Resolved
- Started
- 2026-09-28 13:45 UTC
39 days ago - Last update
- 2026-09-28 14:11 UTC
39 days ago - Duration
- 25m
Timeline
-
28 Sep · 14:11 UTC
🟠 Resolved
atom
Sep 28, 14:11 UTC
Resolved - This incident has been resolved.
Sep 28, 13:44 UTC
Monitoring - A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation. -
28 Sep · 14:00 UTC
🟠 Monitoring
atom
Sep 28, 13:44 UTC
Monitoring - A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation. -
28 Sep · 13:59 UTC
🟠 Monitoring
atom
Sep 28, 13:44 UTC
Monitoring - A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation. -
28 Sep · 13:55 UTC
🟠 Monitoring
atom
Sep 28, 13:44 UTC
Monitoring - Customers who built or deployed between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some customers builds succeeded but resulted in deployments which failed and served 500s. Any customers experiencing runtime errors should re-deploy their projects. -
28 Sep · 13:45 UTC
🟠 Monitoring
atom
Sep 28, 13:44 UTC
Monitoring - Customers who built or deployed between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some customers builds succeeded but resulted in deployments which failed and served 500s. Any customers experiencing runtime errors should re-deploy their projects.
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.