Is Netlify down?
Right now
No. Netlify is operational.
No incidents reported.
Read from www.netlifystatus.com · every 120s
For agents
proceed
Proceed.
GET upbutler.com/status/netlify/status.agent.json
MCP: upstream_status {"service":"netlify"}
Builds, CDN, Functions and DNS.
What Netlify reports
Operational
Taken as is from Netlify's own status page API. Incident titles and component names below are theirs.
Open www.netlifystatus.comUpButler's independent probe
API edge is answeringHTTP 401 · 615 ms
One request without credentials to api.netlify.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
Netlify components
39 operational
- High-Performance Edge NetworkOperational
- Standard Edge NetworkOperational
- Origin ServersOperational
- Build PipelineOperational
- Netlify Application UIOperational
- APIOperational
- Hosted DNSOperational
- PrerenderingOperational
- IdentityOperational
- Netlify FunctionsOperational
- AnalyticsOperational
- Log DrainsOperational
- Collaborative Deploy PreviewsOperational
- Git GatewayOperational
- Edge FunctionsOperational
- Netlify Image CDNOperational
- Netlify BlobsOperational
- Netlify ObservabilityOperational
- Netlify ConnectOperational
- Netlify Create APIOperational
- Visual EditorOperational
- Netlify FormsOperational
- Netlify Support ForumsOperational
- Netlify HelpdeskOperational
- Domain PurchasingOperational
- BillingOperational
- Agent RunnersOperational
- AI GatewayOperational
- Live TunnelOperational
Third-Party Services
- Atlassian Bitbucket APIOperational
- Atlassian Bitbucket WebhooksOperational
- Atlassian Bitbucket SSHOperational
- npm, Inc. Registry ReadsOperational
- GitHub API RequestsOperational
- GitHub WebhooksOperational
- GitHub Git OperationsOperational
- NS1 APIOperational
- NS1 Management PortalOperational
- Name.comOperational
Netlify incidents, last 90 days
4 finished incidents seen since UpButler started tracking on 2026-10-10. A typical one lasted under a minute; the longest 50 min.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| Elevated Edge Function Errors | none | under a minute | |
| Elevated error rates for AI Gateway | none | under a minute | |
| Error accessing Netlify-hosted sites | minor | 50 min | |
| Error accessing Netlify-hosted sites | none | under a minute |
Tell your outage from Netlify's
Declare that your project depends on Netlify. 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.
# upbutler.yaml
dependencies:
- netlifycurl -s https://upbutler.com/status/netlify/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "netlify",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Netlify down right now?
- No. As of 2026-10-10 05:12 UTC, Netlify is operational. 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 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Netlify's words.
- 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). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Netlify reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Netlify status?
- Fetch https://upbutler.com/status/netlify/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"}, 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.
More in hosting and compute
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.