Get told when Netlify breaks
One email when Netlify reports an incident, one when it is resolved. No account, nothing else.
Used only for Netlify status alerts. Every email carries an unsubscribe link.
Netlify components
39 of 39 operational
Show all 39 components
- High-Performance Edge NetworkOperational
- Atlassian Bitbucket APIOperational
- Standard Edge NetworkOperational
- Atlassian Bitbucket WebhooksOperational
- Atlassian Bitbucket SSHOperational
- Origin ServersOperational
- Build PipelineOperational
- npm, Inc. Registry ReadsOperational
- GitHub API RequestsOperational
- Netlify Application UIOperational
- APIOperational
- GitHub WebhooksOperational
- Hosted DNSOperational
- GitHub Git OperationsOperational
- PrerenderingOperational
- NS1 APIOperational
- IdentityOperational
- NS1 Management PortalOperational
- Netlify FunctionsOperational
- Name.comOperational
- 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
Recent Netlify incidents
The most recent incidents Netlify has published, newest first.
- critical
Elevated HTTP 500 errors serving sites and the Netlify UI
Resolved in 0m
- major
Elevated Build Errors
Resolved in 25m
Netlify status: common questions
- Is Netlify down right now?
- Netlify's status feed has stopped refreshing — the readings below are the last ones we received. All 39 components are operational. No incident is open. This page mirrors the official Netlify status feed. PingView last read it on August 31, 2026 at 11:40 AM UTC.
- Where does this Netlify status data come from?
- Directly from the official Netlify status page at www.netlifystatus.com. PingView polls that feed, records every incident it publishes and keeps a permanent, dated history that the vendor page itself does not retain.
- How often is this page updated?
- PingView reads the official Netlify feed and rebuilds this page every 5 minutes. The timestamp of the last successful read is shown next to the status, so you can tell how fresh the answer is.
- Netlify reports everything as operational, but my integration is failing. What now?
- A vendor status page is a global signal, not a per customer one. Partial failures, regional routing problems and issues that hit a single account often never appear on it. Check the Netlify endpoints your own product calls, from more than one region, and compare your timeline against the vendor's. That is what PingView does, and the SLA calculator turns the resulting downtime into a number you can put in front of a client.