We’ve been experiencing random HTTP 500 errors in two of our production Next.js applications deployed on Vercel. The issue started around October 26th, 2025, and we haven’t been able to determine a clear cause yet.
Setup overview
App 1:
Next.js 14.2.5
Node.js 20
Fluid Compute: Disabled
Region:eu-central-1
Stable in production for several months, with no recent code changes. The issue started appearing recently without any configuration changes.
App 2:
Next.js 15.5.2
Node.js 22
Fluid Compute: Enabled
Region:eu-central-1
Newer app in production. We initially suspected Inngest, since the problem appeared soon after adding it, but the errors persist even after uninstalling it.
Both applications use the Inngest SDK, and both connect to Supabase (also hosted in the same region). Supabase logs show no connection errors or abrupt disconnections, so the database layer doesn’t appear to be involved.
Error details
The issue occurs randomly during HTTP requests. In many cases, it affects the same endpoint (the one typically hit first when users open the app), but it has also occurred on other routes.
In the Vercel logs, we consistently see entries like:
Node.js process exited with signal: 6 (SIGABRT) (core dumped)
or occasionally:
Node.js process exited with signal: 11 (SIGSEGV) (core dumped)
Immediately after, we see low-level memory errors such as:
double free or corruption (out)
corrupted double-linked list
munmap_chunk(): invalid pointer
free(): invalid pointer
Additional notes
No corresponding errors appear in our application logs.
The issue occurs sporadically, typically under normal production load (not under heavy stress).
The same code runs fine locally without crashes.
This started recently without code changes, which makes us suspect a potential platform or runtime-level issue (Node or infrastructure related).
Has anyone else seen similar behavior recently, especially in the eu-central-1 region?
Any guidance or insights from would be greatly appreciated. In particular, how to debug these kind of low level errors in production
Negative. I thought of an error with App2 (recently released to production). But then suddenly started happening in App1, which has been stable for several months.
Are you using Supabase or Inngest in your app by any chance?
I really hope someone can shed some light into this matter
We’ve been facing the exact same issue for the past few weeks — random HTTP 500s with SIGABRT and SIGSEGV crashes on Vercel (also in eu-central-1). It started suddenly without any code or dependency changes.
After a lot of trial and error, the following changes seem to have stabilized things on our side:
@pawlean Is the Vercel team aware of this issue? And to which regions it applies? It’d be great if team Vercel could provide some insight into what’s happening and how to resolve it.
Had the exactly issues. No major changes recently for our code and it started to show up around 9/28. Also encountering something like double free or corruption (out) along with that (SIGABRT / SIGSEGV) error.
We’re seeing the same issue. A mix of Node.js process exited with signal: 11 (SIGSEGV) (core dumped). and Node.js process exited with signal: 6 (SIGABRT) (core dumped).No other logs.
I was using Node 22.x, I switched to 20.x and the problem persists, so I believe the issue isn’t the Node version.
I’m using Prisma version 5.14.0, as previously mentioned, it could have something to do with it.
. Will keep trying.