Is Netlify edge network down right now?

No. As of 2026-10-10 07:19 UTC, Netlify edge network is up. This page reads the status again every 2 minutes.

Where does this status come from?

From Netlify's own status page API at https://www.netlifystatus.com. UpButler reads it once for everyone (not once per visitor) every 2 minutes with conditional requests, and shows it unchanged: incident titles and component names are Netlify's words. Their page covers more than this page shows; it is narrowed to the parts that concern Netlify edge network.

What does UpButler's own Netlify check prove?

Every two minutes UpButler sends one request without credentials to the Netlify API edge (api.netlify.com) from eu-central. Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.

Can I get an alert when Netlify edge network goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Netlify reports an incident that affects Netlify edge network and one when it is over. There is also an RSS feed at https://upbutler.com/status/netlify/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check Netlify edge network status?

Fetch https://upbutler.com/status/netlify/edge-network/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"netlify","component":"edge-network"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Netlify's?

Add "netlify" to the dependencies of your UpButler workspace. When one of your monitors fails while Netlify has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Netlify edge network down?

Netlify edge network is up

Right now

No. Netlify edge network: no incidents reported.

Last checked 51 s ago (2026-10-10 07:19 UTC) from www.netlifystatus.com · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/netlify/edge-network/status.agent.json

MCP: upstream_status {"service":"netlify","component":"edge-network"}

The CDN that serves sites.

Part of Netlify status. Covers 2 of their components: High-Performance Edge Network, Standard Edge Network.

What Netlify says

Operational

Taken as is from Netlify's own status page API. Incident titles and component names below are theirs. Narrowed to what concerns Netlify edge network.

Open www.netlifystatus.com

What UpButler measured

API edge is answeringHTTP 401 · 462 ms

One request without credentials to api.netlify.com every two minutes, from eu-central (one location, not a global view). An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed. The probe is for Netlify as a whole, not for Netlify edge network specifically.

Checked 2 min ago · up since 2026-10-10 01:23 UTC

Netlify edge network: what Netlify lists

2 operational

High-Performance Edge NetworkOperational
Standard Edge NetworkOperational

2026-07-131 of 12 days with an incidenttoday

Each bar is a day, coloured by the worst incident Netlify reported for Netlify edge network. It is their incident record, not a measurement of uptime.

Incidents: 2; 0 major or critical
Typical time to resolve: —; median, needs 3 incidents
Nine in ten within: —; 90th percentile
Longest: 50 min; record since 2026-09-29

Started (UTC)	Incident	Impact	Lasted
2026-10-05 12:44	Error accessing Netlify-hosted sites	minor	50 min
2026-09-29 08:46	Error accessing Netlify-hosted sites	none	under a minute

Get alerted when Netlify edge network goes down

No account. One email when Netlify reports an incident that affects Netlify edge network, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Netlify as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Netlify edge network's current status in a README or an internal wiki. It updates by itself.

[![Netlify edge network status](https://upbutler.com/status/netlify/badge.svg?component=edge-network)](https://upbutler.com/status/netlify/edge-network)

Tell your outage from Netlify's

Declare that your project depends on Netlify edge network. When one of your monitors fails while Netlify has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - service: netlify
    components: ["High-Performance Edge Network", "Standard Edge Network"]

Ask before you retry

curl -s https://upbutler.com/status/netlify/edge-network/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "netlify",
  "component": {
    "slug": "edge-network",
    "name": "Netlify edge network"
  },
  "verdict": "proceed",
  "status": "operational",
  "reason": "Netlify edge network: no incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": {
    "state": "up",
    "statusCode": 401
  }
}

Questions

Is Netlify edge network down right now?: No. As of 2026-10-10 07:19 UTC, Netlify edge network is up. This page reads the status again every 2 minutes.
Where does this status come from?: From Netlify's own status page API at https://www.netlifystatus.com. UpButler reads it once for everyone (not once per visitor) every 2 minutes with conditional requests, and shows it unchanged: incident titles and component names are Netlify's words. Their page covers more than this page shows; it is narrowed to the parts that concern Netlify edge network.
What does UpButler's own Netlify check prove?: Every two minutes UpButler sends one request without credentials to the Netlify API edge (api.netlify.com) from eu-central. Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work from there. It does not prove that authenticated requests succeed, and it is one location, not a global view. It is most useful when it fails before their status page changes; the page then says so.
Can I get an alert when Netlify edge network goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Netlify reports an incident that affects Netlify edge network and one when it is over. There is also an RSS feed at https://upbutler.com/status/netlify/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Netlify edge network status?: Fetch https://upbutler.com/status/netlify/edge-network/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"netlify","component":"edge-network"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Netlify's?: Add "netlify" to the dependencies of your UpButler workspace. When one of your monitors fails while Netlify has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Netlify. Status and incident text belong to Netlify and are read from their public status source; the probe result is UpButler's own measurement.