Is Netlify down?
No, Netlify is not down.
Netlify’s status page reports no incidents, api.netlify.com responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsnetlifystatus.com
- Reachable6 of 6 regionsNetlify API · api.netlify.com
- Reports in the last hour0Normal
Netlify’s status page
From netlifystatus.com. Read at
- High-Performance Edge NetworkOperational
- Atlassian Bitbucket API Third-Party ServicesOperational
- Standard Edge NetworkOperational
- Atlassian Bitbucket Webhooks Third-Party ServicesOperational
- Atlassian Bitbucket SSH Third-Party ServicesOperational
- Origin ServersOperational
- Build PipelineOperational
- npm, Inc. Registry Reads Third-Party ServicesOperational
Show all 42 components
- GitHub API Requests Third-Party ServicesOperational
- Netlify Application UIOperational
- APIOperational
- GitHub Webhooks Third-Party ServicesOperational
- Hosted DNSOperational
- GitHub Git Operations Third-Party ServicesOperational
- PrerenderingOperational
- NS1 API Third-Party ServicesOperational
- IdentityOperational
- NS1 Management Portal Third-Party ServicesOperational
- Netlify FunctionsOperational
- Name.com Third-Party ServicesOperational
- 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
- Netlify DatabaseOperational
- Edge Function LogsOperational
- Function LogsOperational
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 430 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.netlify.com)
By region
| Region | Netlify API api.netlify.com |
|---|---|
| N. Virginia us-east-1 | 401 · 61 ms |
| Oregon us-west-2 | 401 · 216 ms |
| Frankfurt eu-central-1 | 401 · 422 ms |
| Singapore ap-southeast-1 | 401 · 874 ms |
| Tokyo ap-northeast-1 | 401 · 633 ms |
| São Paulo sa-east-1 | 401 · 507 ms |
Two regions check Netlify every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Netlify ourselves since Oct 28, 2026. Earlier days come from its status page.
19 days with problems in the last 90 days.
Recent incidents
Incidents: 10 in the last 30 days and 19 in the last 90, lasting a median of 50 min.
- Elevated Build Errors and Agent Runner failuresPartial outage56 min
- Delays in build logs appearing in the UIDegraded11 h 15 min
- Delayed Edge Functions and Functions logsDegraded3 h 50 min
- Delays in build logs appearing in the UIDegraded22 h 25 min
- Agent Runner failuresPartial outage1 h 8 min
- Elevated Build ErrorsDegraded51 min
- Elevated Edge Function ErrorsDegradedunder 1 min
- Elevated error rates for AI GatewayDegradedunder 1 min
- Error accessing Netlify-hosted sitesDegraded50 min
- Error accessing Netlify-hosted sitesDegradedunder 1 min
If Netlify isn’t working for you
Netlify is a platform for building, deploying and hosting websites and web apps, with serverless functions and a global CDN.
Common Netlify errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
Site not available. This site was paused as it reached its usage limits. | The team used up its plan's credits or usage, so Netlify paused its projects. | Your side | Buy more credits, upgrade, or wait for the next billing cycle; contact support if it stays paused. Source |
Page not found | Netlify served its 404 because the site is published from the wrong folder or the path does not exist. | Your side | Check the publish directory in your build settings and your redirects. Source |
Build fails with exit status 128 | Netlify does not have permission to clone the repository. | Your side | Relink the repository or fix the Git provider permissions. Source |
command not found | A build command such as gulp or jekyll is not installed in the build environment. | Your side | Add the tool to your project dependencies. Source |
Is it just you?
- Check whether the problem is the live site or builds: deploys can queue or fail while sites keep serving.
- Open another Netlify-hosted site; if it loads, the problem is your site's settings or usage.
- Check the team's usage page; a paused site shows "Site not available" to every visitor.
- Check netlifystatus.com for incidents affecting builds, the CDN or functions.
Alternatives to Netlify
Questions
Netlify pauses projects when a team reaches its plan's usage limits. Add credits, upgrade, or wait for the billing cycle to reset; Netlify's community forum points to support for sites that stay paused.
Builds wait in a team queue when you exceed your concurrent build capacity, and in a system queue when Netlify's build capacity is busy. Queued builds start as capacity frees up.
Sources: docs.netlify.com, answers.netlify.com, netlifystatus.com
Get alerted when Netlify breaks your app.
If your product or your team depends on Netlify, its outage is your outage, and your users will blame you, not Netlify. Point a Site Qwality monitor at the Netlify endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.