Ongoing incident: elevated errors across multiple services

Help
46

I have been trying to deploy my changes on production but it keeps failing without any error. I have tried vercel build as well. The build is always successful but in the very end is says An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help

Vercel Logs:
16:26:46.412 Running build in Washington, D.C., USA (East) – iad1
16:26:46.421 Build machine configuration: 2 cores, 8 GB
16:26:46.491 Retrieving list of deployment files…
16:26:47.221 Downloading 122 deployment files…
16:26:49.142 Restored build cache from previous deployment (FgWgx8x4SzZKP6v4YaoCJCqMut3B)
16:26:49.530 Running “vercel build”
16:26:49.916 Vercel CLI 48.2.9
16:26:50.289 Installing dependencies…
16:26:51.297
16:26:51.298 added 2 packages in 894ms
16:26:51.298
16:26:51.299 39 packages are looking for funding
16:26:51.299 run npm fund for details
16:26:51.310 Detected Next.js version: 14.2.7
16:26:51.314 Running “npm run build”
16:26:51.437
16:26:51.438 > casino24@0.1.0 build
16:26:51.438 > next build
16:26:51.438
16:26:52.173 ▲ Next.js 14.2.7
16:26:52.174 - Environments: .env
16:26:52.175
16:26:52.193 Creating an optimized production build …
16:27:19.473 Browserslist: caniuse-lite is outdated. Please run:
16:27:19.473 npx update-browserslist-db@latest
16:27:19.473 Why you should do it regularly: GitHub - browserslist/update-db: CLI tool to update caniuse-lite to refresh target browsers from Browserslist config
16:27:21.811 ✓ Compiled successfully
16:27:21.813 Linting and checking validity of types …
16:27:29.004 Collecting page data …
16:27:30.779 Generating static pages (0/31) …
16:27:32.456 Generating static pages (7/31)
16:27:34.273 Generating static pages (15/31)
16:27:34.910 Generating static pages (23/31)
16:27:35.234 ✓ Generating static pages (31/31)
16:27:35.436 Finalizing page optimization …
16:27:35.436 Collecting build traces …
16:27:37.857
16:27:37.868 Route (app) Size First Load JS
16:27:37.869 ┌ ○ / 6.31 kB 130 kB
16:27:37.869 ├ ○ /_not-found 876 B 88.2 kB
16:27:37.870 ├ ○ /404 294 B 94.4 kB
16:27:37.870 ├ ○ /about-us 3.44 kB 116 kB
16:27:37.870 ├ ƒ /blog/[slug] 2.8 kB 123 kB
16:27:37.870 ├ ○ /blogs 3.09 kB 129 kB
16:27:37.871 ├ ○ /bonuses 2.17 kB 122 kB
16:27:37.871 ├ ○ /casinos 2.07 kB 131 kB
16:27:37.871 ├ ○ /details 4.7 kB 125 kB
16:27:37.871 ├ ○ /games 2.26 kB 123 kB
16:27:37.871 ├ ○ /imprint 2.09 kB 114 kB
16:27:37.872 ├ ○ /play-responsibly 4.06 kB 116 kB
16:27:37.872 ├ ○ /sports-betting 3.46 kB 130 kB
16:27:37.872 ├ ○ /terms-and-conditions 4.33 kB 116 kB
16:27:37.873 ├ ○ /vips 352 B 87.7 kB
16:27:37.873 ├ ○ /vips/add-edit-blog 15.8 kB 119 kB
16:27:37.873 ├ ○ /vips/add-edit-bonus 5.62 kB 109 kB
16:27:37.873 ├ ○ /vips/add-edit-casino 4.36 kB 120 kB
16:27:37.874 ├ ○ /vips/add-edit-exclusive-deal 32.1 kB 148 kB
16:27:37.874 ├ ○ /vips/add-edit-game 5.49 kB 109 kB
16:27:37.874 ├ ○ /vips/add-edit-sport 4.43 kB 120 kB
16:27:37.874 ├ ○ /vips/auth 5.12 kB 104 kB
16:27:37.875 ├ ○ /vips/blogs-list 6.74 kB 110 kB
16:27:37.875 ├ ○ /vips/bonuses-list 4.77 kB 108 kB
16:27:37.875 ├ ○ /vips/casinos-list 5.77 kB 109 kB
16:27:37.875 ├ ○ /vips/exclusive-deals-list 4.87 kB 108 kB
16:27:37.876 ├ ○ /vips/games-list 4.88 kB 108 kB
16:27:37.876 ├ ○ /vips/mainpage 76 kB 168 kB
16:27:37.876 ├ ○ /vips/settings 4.57 kB 108 kB
16:27:37.877 └ ○ /vips/sports-list 5.76 kB 109 kB
16:27:37.877 + First Load JS shared by all 87.4 kB
16:27:37.877 ├ chunks/7023-64d7d1cf57d78cc4.js 31.6 kB
16:27:37.877 ├ chunks/fd9d1056-356287bdcf1f524a.js 53.6 kB
16:27:37.883 └ other shared chunks (total) 2.16 kB
16:27:37.883
16:27:37.883
16:27:37.883 ○ (Static) prerendered as static content
16:27:37.883 ƒ (Dynamic) server-rendered on demand
16:27:37.883
16:27:38.014 Traced Next.js server files in: 33.659ms
16:27:38.182 Created all serverless functions in: 168.324ms
16:27:38.200 Collected static files (public/, static/, .next/static): 10.722ms
16:27:38.356 Build Completed in /vercel/output [48s]
16:27:38.543 Deploying outputs…
16:28:14.186 An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help

47
Vercel Deployment Issue

Deployment Fails with “An unexpected error happened when running this build”

Hello Vercel Team,

I’m encountering a deployment issue on my Next.js project. The build completes successfully, but during deployment I receive the following error:

An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error.

Project Details:

Additional Info:

  • There is an ongoing incident on the Vercel status page affecting multiple services, including builds and serverless functions, particularly in the IAD1 region (Washington DC).
  • Build logs show: 
    
Collected static files (public/, static/, .next/static): 12.743ms
Build Completed in /vercel/output [37s]
Deploying outputs...
An unexpected error happened when running this build...
  • Local build works fine; this appears to be a platform-related issue.

I’m reporting this deployment failure so the team can monitor the impact. Please let me know if additional information is needed.

Thank you for your help.

— Swarup Baral

48

An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error.

49

Current: Build completes successfully, but deployment fails during “Deploying outputs…” with “An unexpected error happened when running this build.”
Expected: Deployment should complete after a successful build.

Steps:
Push commit ca2b33d to main on GitHub.
Vercel installs deps and runs Next.js build (15.0.1) successfully.
During “Deploying outputs…”, deployment fails with an unexpected error.
Local: npm run build succeeds locally with only non-blocking warnings about Edge runtime and Supabase client.

Project name: school-management-system
Repo: https://github.com/DRKIMULI/school-management-system
Branch: main
Commit SHA: ca2b33d
Framework: Next.js 15.0.1
Package manager: npm
Node: (Vercel default for Next 15)
Region: Portland, USA (West) – pdx1
Deployment URL: [paste the failed deployment URL here]
Team/Account: [your Vercel team/account name]
Notes:
Only warnings shown: Edge Runtime complaints from @supabase/supabase-js and @supabase/realtime-js.
Dependencies updated to latest minor/patch; no major upgrades.
108 pages generated; no compile errors.

50

Error: An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help

51

I’m encountering a deployment issue where my build fails during the npm install phase with the following error:

npm error command failed
npm error command sh -c node ./postinstall.js
npm error path /vercel/path0/node_modules/ngrok

The log also shows network/TLS phase timeouts:

npm error phases: { wait: 0, dns: 24, tcp: undefined, tls: undefined, request: undefined, … }

52

The deployment was successful earlier, yet, once the AWS server around the wrold crashed, I keep encountering with issues with deployment

53

An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. If the problem persists, please contact Vercel Support https://vercel.com/help

Same here - unable to work - concerning what this kind of crash causes this much of a domino around the world.

54

Same for my hobby project

55

Also running into what seems to be the exact same issue now

56

Guess it’s time to step outside, touch some grass, and breathe in the autumn. :person_in_lotus_position:

1 Like
57

Running into the same issue right now for my hobby page!

58

My build is (finally) passing now and it seems like AWS has made some fixes: https://health.aws.amazon.com/health/status

1 Like
59

It would have been great if you had attached the link to the status page.

60

Thanks for the feedback! The incident page is linked in the post here.

61

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.