outages.live
Live
NetlifyIncident · 2026-10-08 14:34 UTC

Elevated Edge Function Errors

ResolvedOfficial update

Between 13:16 and 13:24 UTC some requests to sites that use Edge Functions experienced increased latency and an elevated rate of 502 errors. This incident has been resolved.

The latest update from Netlify.

State

Resolved

Started

24 d ago

2026-10-08 14:34 UTC

Lasted

1 min

until 2026-10-08 14:34 UTC

Worst impact

Notice

Timeline

1 update
14:3414:3414:3414:3414:35
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Netlify

Resolved2026-10-08 14:34 UTC

Between 13:16 and 13:24 UTC some requests to sites that use Edge Functions experienced increased latency and an elevated rate of 502 errors. This incident has been resolved.

Affected components

1
Edge Functions

Netlify in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

17

Days with an incident

15

Median duration

51 min

This incident

100% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

11 h 16 min
median 51 min
90 days agoToday

Other Netlify incidents

All incidents

Netlify·Elevated Build Errors and Agent Runner failures

The issue affecting builds and agent runs has been resolved.

Resolvedresolved 5 d ago

Netlify·Delays in build logs appearing in the UI

This incident has been resolved.

Resolvedresolved 5 d ago

Netlify·Delayed Edge Functions and Functions logs

This incident has been resolved.

Resolvedresolved 10 d ago

Netlify·Delays in build logs appearing in the UI

The issue causing delays in build logs appearing in the Netlify UI has been resolved.

Resolvedresolved 10 d ago

Netlify·Agent Runner failures

This incident has been resolved.

Resolvedresolved 12 d ago

Follow Netlify

Your coding agent knows when Netlify is down, and tells you when a failure is theirs, not yours. You can also get Netlify incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "netlify" and tell me if Netlify has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=netlify
Slack
/feed subscribe https://outages.cc/feed.xml?providers=netlify

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane