The site suddenly returns Internal Server Error

Support
1

My site https://fincaguarumo.com (hosted by Netlify via fincaguarumo.netlify.app, a next.js app) suddenly returns a 500 error.

In the logs, I can see only this:

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

I have not changed anything recently, I do not have any custom functions. I have no idea how to debug this error as it seems to stem from Netlify itself and not something on my end.

Just to be sure, I triggered a manual deploy without cache, updated the @netlify/plugin-nextjs to 5.12.0, but to no avail.

The app uses next.js 15.

Is there anything else that can be done on my end?

5 Likes
Edge Runtime Function Error
Edge Runtime Function Error
2

I am getting the same error!

3

same here, i guess its not a problem on our end

4

Same thing here, no idea whats going on!

Aug 11, 02:15:14 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

5

Would this appear here as an operational issue? https://www.netlifystatus.com/

6

same here,i doing noting

Aug 12, 01:26:13 AM: 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 Aug 12, 01:28:56 AM: 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

7

Same here! There are no error logs in my function handler either; logs just stop at around 11:07 AM US Central time.

Site: https://heroscapehelper.com

8

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
9

cc @hrishikesh @Andrew.H @luke @sid.m @serhalp looks like a Netlify outage, maybe you can update the status page at https://www.netlifystatus.com/ ? And let the engineers know if theyā€™re not already awareā€¦

3 Likes
10

Iā€™m in the same situation. Disappointed that Netlify Status is showing nothing useful.

1 Like
11

Posted on Twitter and Bluesky in case that will help anyone at Netlify notice faster:

3 Likes
12

Similar errors, our production site is totally down.

Aug 11, 01:43:43 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

13

Same. If you can disable/comment out any [[edge_functions]] in your netlify.toml that will temporarily fix it until they fix stuff on their side.

1 Like
14

Also happening to me, thought this was an error in my code, lol. We donā€™t use deno either. https://bloxora.com went down about 1-3 hours ago.

15

Workaround

For us, our edge handler was related to our Middleware. The Netlify Next.js adapter runs Middleware on edge functions.

Because Next.js now has Node.js Middleware support, I tried upgrading to Next.js canary version v15.4.2-canary.35 and then added the runtime: ā€˜nodejsā€™ like below to my configuration in middleware.ts:

export const config = {
  runtime: 'nodejs',

After this change, weā€™re back up: https://upleveled.io/

However, Node.js Middleware is marked as ā€œnot supported yetā€ in the Netlify docs: Next.js on Netlify | Netlify Docs.

1 Like
16

Hi all, thanks so much for your patience here. This issue has now been resolved. You can view the retroactive statuspage here: Netlify Status - Increase in Edge Function errors

3 Likes
17

Hi all, Netlify engineer here.

I just wanted to apologise for the inconvenience this may have caused you. The issue was caused by a change to our system that we started rolling out to a subset of our customers, and our automated monitoring failed to catch a problem in that code.

Weā€™re putting measures in place to make sure we can respond much quicker should an incident like this ever occur again.

Iā€™m sorry again for the stress and confusion and thanks for your patience.

1 Like