Edge Runtime Function Error

Support
1

My code was working fine for weeks, up until hours ago. I’ve made no new updates. Randomly the site displays in black “Internal Server Error”, there’s no browser logs or function logs (blank), our debug logs are gone as well. Build succeeds fine, however in Edge Functions it says:

Aug 11, 01:33:38 PM: error  Error handling request: TypeError: functions is not a function
    at file:///root/src/bootstrap/server.ts:53:45
    at mapped (ext:deno_http/00_serve.ts:407:24)
    at mapped (ext:deno_http/00_serve.ts:513:16)
    at ext:deno_http/00_serve.ts:729:29
    at eventLoopTick (ext:core/01_core.js:178:7)
    at async netlify:bootstrap-stage1:4:1

Anyone know how to fix this? I don’t think it’s on my end.

3 Likes
2

Yes, also experiencing this - seems like starting at around 18:08 CEST (UTC+2), our Next.js site https://upleveled.io went down (also, currently down):

Screenshot 2025-08-11 at 19.09.40
Screenshot 2025-08-11 at 19.09.401178×356 12.5 KB

In the Edge Functions logs, I have this:

Aug 11, 07:40:22 PM: error  Error handling request: TypeError: functions is not a function
    at file:///root/src/bootstrap/server.ts:53:45
    at mapped (ext:deno_http/00_serve.ts:407:24)
    at mapped (ext:deno_http/00_serve.ts:513:16)
    at ext:deno_http/00_serve.ts:729:29
    at eventLoopTick (ext:core/01_core.js:178:7)
    at async netlify:bootstrap-stage1:4:1

We don’t use Deno, so it looks like a problem on the Netlify side.

Any Netlify support people around? Could you update the Netlify Status page with the outage? https://www.netlifystatus.com/

1 Like
3

Looks like others are reporting over here:

2 Likes
4

Thanks! I was trying to fix stuff in my code thinking it was an me issue lol.

5

Same here. This morning my Nuxt (Vue 3) app was running just fine. Rebuilding and redeploying without cache completed successfully but I’m still getting the Internal Server Error screen when accessing the app and the same error message in the edge function logs.

Not using Deno either, it’s definitely on Netlify’s side

6

Same issue here. Our frontend is suddenly just returning “Internal Server Error”.

Fortunately I was able to just turn off the edge function for now until I have a better solution.

Has anyone been able to solve this?

7

It’s probably a problem on Netlify’s side, more details over here:

8

Hi all, thanks so much for your patience here. This issue has been resolved, you can view the retroactive status page here: https://www.netlifystatus.com/incidents/b11yy3qmb0md

1 Like