[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Help](/c/help/9) # Ongoing incident: elevated errors across multiple services 1648 views · 19 likes · 55 posts Joris (@joris-kopilo) · 2025-10-20 · ♥ 3 \[EDIT5\] I successfully deployed just now, so it seems to work again for me. \[EDIT4\] As of 11:11 UTC, deployments are still not working. Just an FYI for anyone looking at this post. \[EDIT3\] I said it too soon I guess. My websites are back online, but I can’t deploy, similar to other posts. I’m also getting: * Build Completed in /vercel/output \[2m\] * Deploying outputs… * 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](https://vercel.com/help) \[EDIT2\] It’s finally back online for me. When that passed, I feel like I should say that 1,5 hours is too long in my opinion. This should not happen to a company as large as Vercel. \[EDIT\] CDN seems to work again, however, now server functions are the problem. So, still internal server errors on all of my websites. Vercel is having a major outage it seems, which is now also crashing all my websites that I’m hosting on Vercel. I’m serving users, so this is quite shit. Vercel.com doesn’t work for me either anymore. I’m going straight to the Something went wrong page. Does anyone else have problems too? xs1990 (@xs1990) · 2025-10-20 same. all sites down.. no matter what vercel jsut changed, can your eng team roll it back? Swarnava Sengupta (@swarnava) · 2025-10-20 · ♥ 2 Hi Ravid, Thanks for bringing this to our attention. I’d be happy to work with you to resolve this. We have a current platform incident affecting several Vercel Products. Our on-call engineers are already working on a fix, and we hope this will be resolved shortly. Apologies for any inconvenience. We will provide more information as soon as we have them here: [https://www.vercel-status.com/incidents/5m5fd7ljhf26](https://www.vercel-status.com/incidents/5m5fd7ljhf26) I appreciate your patience while we work on this. Happy to help with any questions. Enigma (@emmanuelonoja291-411) · 2025-10-20 Hello, Good day, Please I am having deployment issues, no clear error message was provided. ”**Build Failed** An unexpected error happened when running this build. We have been notified of the problem. If you have any questions, please contact Vercel Support https://vercel.com/help “ Kubnot (@kubnot) · 2025-10-20 Experiencing the same issue — I’m unable to access most services. Kubnot (@kubnot) · 2025-10-20 can’t deploy ! 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](https://vercel.com/help) Filipgerm (@filipgerm) · 2025-10-20 Same issue here. I receive the exact same unexpected error message when trying to deploy to production. Andy150104 (@andy150104) · 2025-10-20   I don't understand why there were no errors during deployment before, but now this error suddenly appears. The project used to build and run just fine without any issues, and I haven’t made any major changes that should affect the deployment process. Could someone please help me understand what might be causing this error, or if it’s related to a recent change or a temporary issue on Vercel’s side? Efecaglarr (@efecaglarr) · 2025-10-20 Hi, most of us are getting the same error right now. We're all waiting for the fix. Here's the support link for your instance. https://community.vercel.com/t/an-unexpected-error-happened-when-running-this-build/25265/5?u=efecaglarr Mario Ottmann (@supermario0711) · 2025-10-20 · ♥ 1 I think there is a major outage going on (even beyond Vercel). I think the error you’re seeing is independent of your project. It seems like we simply have to wait I’m afraid. wanglin (@haohuoxing-5267) · 2025-10-20 It turns out that everyone has encountered the same problem. It is also this opportunity that I appeared in the forum to communicate with you guys. I have used Vercel for a long time, and this is my first time to join the forum. Senior Webdeveloper (@senior-webdeveloper) · 2025-10-20 <!-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand the problem! --> <!-- Current versus Expected behavior --> <!-- Code, configuration, and steps that reproduce this issue --> <!-- Project information (URL, framework, environment, project settings) --> When deploying my Reat project and vercel serverless function to vercel, I got below issue, please help me! Thank you. **Build Failed** 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 Mungbeangithub (@mungbeangithub) · 2025-10-20 <!-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to i nclude all detail needed to let others see and understand the problem! --> <!-- Current versus Expected behavior --> <!-- Code, configuration, and steps that reproduce this issue --> <!-- Project information (URL, framework, environment, project settings) -->  ``` ```  Gkings (@geordiekingsbeer-850) · 2025-10-20 Hi there, I am trying to redeploy a new build but I keep getting this build error: An unexpected error happened when running this build. We have been notified of the problem. If you have any questions, please contact Vercel Support https://vercel.com/help Hpt09 (@hpt09) · 2025-10-20 Same here. Redeploying makes it queued but doesn’t proceed. Kinkos1234 (@kinkos1234) · 2025-10-20 Same here. Even my build log ends up as follows; Build Completed in /vercel/output \[38s\] Deploying outputs... Mario Ottmann (@supermario0711) · 2025-10-20 Same for me. I had also an unexpected error when running this build and since then every deployment gets stuck in “queued” - any advice is much appreciated :slight_smile: Cheers, Mario Mario Ottmann (@supermario0711) · 2025-10-20 @swarnava any chance you can help (: Swarnava Sengupta (@swarnava) · 2025-10-20 Hi there, Thanks for bringing this to our attention. I’d be happy to work with you to resolve this. We have a current platform incident affecting several Vercel Products. Our on-call engineers are already working on a fix, and we hope this will be resolved shortly. Apologies for any inconvenience. We will provide more information as soon as we have them here: https://www.vercel-status.com/incidents/5m5fd7ljhf26 I appreciate your patience while we work on this. Happy to help with any questions. Mario Ottmann (@supermario0711) · 2025-10-20 Thank you for working on this. It’s much appreciated. Just for your information (no response expected): It’s no longer stuck in queued but the ominous error persists: An unexpected error happened when running this build. We have been notified of the problem. If you have any questions, please contact Vercel Support [https://vercel.com/help](https://vercel.com/help) Cheers, Mario Gkings (@geordiekingsbeer-850) · 2025-10-20 [quote="swarnava, post:22, topic:25298"] Hi there, Thanks for bringing this to our attention. I’d be happy to work with you to resolve this. We have a current platform incident affecting several Vercel Products. Our on-call engineers are already working on a fix, and we hope this will be resolved shortly. Apologies for any inconvenience. We will provide more information as soon as we have them here: https://www.vercel-status.com/incidents/5m5fd7ljhf26 I appreciate your patience while we work on this. Happy to help with any questions. [/quote] Thanks Swarnava, appreciate the update. To add to Mario’s comment for more context, my build is also no longer stuck being queued but I have this build error mentioning that it may be a transient 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 Swarnava Sengupta (@swarnava) · 2025-10-20 Yes this is due to same incident. Klein (@klein) · 2025-10-20 Same issue here. Also, the current production application is impacted, the auth is not working since early today :frowning: When trying to authenticate, user is redirected to /api/auth/error with: \`\`\` **500**: INTERNAL_SERVER_ERROR Code: `INTERNAL_FUNCTION_INVOCATION_FAILED` \`\`\` Anyone else facing issues with nextauth? — Update #1 - auth is working again :) Bnprt Lab (@bnprt-lab) · 2025-10-20 · ♥ 2 My project can’t be deployed. It stuck in “Queued” status.  sb9 (@sucrebucre) · 2025-10-20 · ♥ 2 Hey @bnprt-lab - same here! Lishobbystore (@lishobbystore) · 2025-10-20 · ♥ 2 Same here! any solution? KhoaTd (@khoaace) · 2025-10-20 · ♥ 2 same here with my project Richard P6l (@richard-p6l) · 2025-10-20 · ♥ 1 Same! Looks like their build & deploy shows a Partial Outage: https://www.vercel-status.com/ Swarnava Sengupta (@swarnava) · 2025-10-20 Hi there, Thanks for bringing this to our attention. I’d be happy to work with you to resolve this. We have a current platform incident affecting several Vercel Products. Our on-call engineers are already working on a fix, and we hope this will be resolved shortly. Apologies for any inconvenience. We will provide more information as soon as we have them here: https://www.vercel-status.com/incidents/5m5fd7ljhf26 I appreciate your patience while we work on this. Happy to help with any questions. Trentluo (@trentluo1-7500) · 2025-10-20 Hi Vercel team, I haven’t been able to deploy my project for about 2 hours. Every time I try to deploy, I get the following error message: ``` 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 ``` I’ve tried multiple redeploys, clearing the cache, and even reconnecting my GitHub repository, but the issue still persists. It was working fine earlier today. Could you please help check if there’s an ongoing issue or something wrong with my project? Drkimuli (@drkimuli) · 2025-10-20 Message: Hello Vercel Support Team, I'm experiencing a deployment failure on my Next.js project despite a successful build. Here are the details: Project Information: Project: school-management-system Repository: github.com/DRKIMULI/school-management-system Branch: main Commit: ca2b33d Framework: Next.js 15.0.1 Issue Description: The build completes successfully (all 108 pages generated, no compilation errors), but deployment fails during the "Deploying outputs..." phase with the 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](https://vercel.com/help?utm_source=support-chat) Build Logs Summary: ✅ Dependencies installed successfully ✅ Next.js build completed without errors ✅ All 108 static pages generated ✅ Build traces collected successfully ❌ Deployment fails during output deployment phase Full Error Context: 12:32:20.590 Build Completed in /vercel/output \[1m\] 12:32:20.867 Deploying outputs... 12:33:01.039 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](https://vercel.com/help?utm_source=support-chat) What I've Tried: The build works perfectly locally (npm run build succeeds) Previous deployments were working fine This appears to be a platform issue rather than a code issue Request: Could you please investigate this deployment failure? The build is successful, so this seems to be an infrastructure issue during the deployment phase. Thank you for your assistance. Best regards, Kimuli Daudi RuntimeFlash (@emperorayush) · 2025-10-20 My frontend deployment failed after commit due to outage, so i redeployed it now and it worked. But its not the same case for my backend deployment, as its showing this 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 <!-- Current versus Expected behavior --> <!-- Code, configuration, and steps that reproduce this issue --> <!-- Project information (URL, framework, environment, project settings) --> Pauline P. Narvas (@pawlean) · 2025-10-20 · ♥ 1 Thank you all for your patience! Cross-posting this for some more info. https://x.com/rauchg/status/1980214247532704165 Prateeksaxena015 6453 (@prateeksaxena015-645) · 2025-10-20 the deployment is failing again and again, i have just change or revert back my next js configs. i have even upgraded my maching still error continues 16:08:25.698 Running build in Portland, USA (West) – pdx1 (Enhanced Build Machine) 16:08:25.699 Build machine configuration: 8 cores, 16 GB 16:08:25.707 Retrieving list of deployment files… 16:08:25.780 Previous build caches not available 16:08:26.103 Downloading 808 deployment files… 16:08:29.905 Using prebuilt build artifacts from .vercel/output 16:08:29.906 Learn more: https://vercel.link/build-output-api 16:08:29.955 Deploying outputs… 16:09:05.169 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 Shamymur 6962 (@shamymur-6962) · 2025-10-20 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 Jehuns 3904 (@jehuns-3904) · 2025-10-20 <!-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand the problem! --> <!-- Current versus Expected behavior --> <!-- Code, configuration, and steps that reproduce this issue --> <!-- Project information (URL, framework, environment, project settings) --> all our services has been down Behubus 9912 (@behubus-9912) · 2025-10-20 · ♥ 1 How do we know when the problem is resolved? Marcoangelo (@marcoangelo) · 2025-10-20 also getting errors on my site and build errors: 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](https://vercel.com/help) Dennis Aboni Atayi (@abden360-2057) · 2025-10-20 Please how do we know its, resolved? Pauline P. Narvas (@pawlean) · 2025-10-20 Keep an eye out on the status page! Iamshujasaqib (@iamshujasaqib) · 2025-10-20 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: https://github.com/browserslist/update-db#readme 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 swarup baral (@swarup-developer-799) · 2025-10-20 <!-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand the problem! --> <!-- Current versus Expected behavior --> <!-- Code, configuration, and steps that reproduce this issue --> <!-- Project information (URL, framework, environment, project settings) --> <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title>Vercel Deployment Issue</title> </head> <body> <h2>Deployment Fails with “An unexpected error happened when running this build”</h2> <p>Hello Vercel Team,</p> <p>I’m encountering a deployment issue on my Next.js project. The build completes successfully, but during deployment I receive the following error:</p> <pre><code>An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error.</code></pre> <h3>Project Details:</h3> <ul> <li><strong>Project Name:</strong> swarup-portfolio</li> <li><strong>Deployment URL:</strong> <a href="https://swarup-portfolio-git-main-swarup-barals-projects.vercel.app">https://swarup-portfolio-git-main-swarup-barals-projects.vercel.app</a></li> <li><strong>Branch:</strong> main</li> <li><strong>Node.js Version:</strong> 18.x</li> <li><strong>Local Build:</strong> Successful (<code>npm run build</code> completes without errors)</li> <li><strong>Deployment Timestamp:</strong> [Insert exact date/time of deployment attempt]</li> </ul> <h3>Additional Info:</h3> <ul> <li>There is an ongoing incident on the Vercel status page affecting multiple services, including builds and serverless functions, particularly in the <code>IAD1</code> region (Washington DC).</li> <li>Build logs show: <pre><code> 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... </code></pre> </li> <li>Local build works fine; this appears to be a platform-related issue.</li> </ul> <p>I’m reporting this deployment failure so the team can monitor the impact. Please let me know if additional information is needed.</p> <p>Thank you for your help.</p> <p><strong>— Swarup Baral</strong></p> </body> </html> Dulkifal (@dulkifal) · 2025-10-20 An unexpected error happened when running this build. We have been notified of the problem. This may be a transient error. <!-- Current versus Expected behavior --> <!-- Code, configuration, and steps that reproduce this issue --> <!-- Project information (URL, framework, environment, project settings) --> Drkimuli (@drkimuli) · 2025-10-20 <!-- Questions that get answered the fastest are the ones with relevant info included in the original post. Be sure to include all detail needed to let others see and understand the problem! --> 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. Dennis Aboni Atayi (@abden360-2057) · 2025-10-20 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 Commoncapital 5928 (@commoncapital-5928) · 2025-10-20 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, … } <!-- Project information (URL, framework, environment, project settings) --> Commoncapital 5928 (@commoncapital-5928) · 2025-10-20 The deployment was successful earlier, yet, once the AWS server around the wrold crashed, I keep encountering with issues with deployment Arundne (@arundne) · 2025-10-20 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](https://vercel.com/help) Same here - unable to work - concerning what this kind of crash causes this much of a domino around the world. Lonli Lokli (@lonli-lokli) · 2025-10-20 Same for my hobby project eleetyson (@eleetyson) · 2025-10-20 Also running into what seems to be the exact same issue now ledev (@lnxav) · 2025-10-20 · ♥ 1 Guess it’s time to step outside, touch some grass, and breathe in the autumn. :person_in_lotus_position: Gnick18 (@gnick18) · 2025-10-20 Running into the same issue right now for my hobby page! eleetyson (@eleetyson) · 2025-10-20 · ♥ 1 My build is (finally) passing now and it seems like AWS has made some fixes: https://health.aws.amazon.com/health/status Behubus 9912 (@behubus-9912) · 2025-10-21 It would have been great if you had attached the link to the status page. Pauline P. Narvas (@pawlean) · 2025-10-21 [quote="Swarnava Sengupta, post:3, topic:25298, username:swarnava"] https://www.vercel-status.com/incidents/5m5fd7ljhf26 [/quote] Thanks for the feedback! The incident page is linked in the post here.
