Live / Netlify / Incident
Netlify: Delayed Edge Functions and Functions logs
Netlify · netlify.comMinor incidentResolved2026-10-22 20:10 UTC
Public — what happened
Summary
Netlify said that logs for Edge Functions and Functions covering roughly 13:58 to 15:35 UTC on 2026-10-22 might show up late in its web interface and in log drains. The company stated that the actual function and edge function requests were not affected, only the logs. Netlify said at 16:19 UTC that it was working through the backlog, and the incident was marked resolved at 20:10 UTC. It rated the issue as minor and did not state a cause in the text provided.
Affected
Edge Function Logs, Function Logs
Timeline
- Started — 2026-10-22 16:19 UTC
- Monitoring — 2026-10-22 16:19 UTC
- Resolved — 2026-10-22 20:10 UTC · 3h 51m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Netlify against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Netlify: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Netlify report →
More from Netlify
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.