Is Netlify down?
No, Netlify is up right now
Both signals agree: the official status feed and our own check.
Request to www.netlify.com, 3 min ago. 258 of 288 checks in the last 24 hours succeeded, median 654 ms.
Is Netlify working for you?
One click, no account. It helps others see whether the problem is widespread.
Response time, last 24 hours
measured from our server in GermanyWorks for everyone else? Fix it on your side
- Check whether it is only this device. Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service.
- Test from the command line. Check name resolution and the route, to see where the connection stops.
nslookup netlify.com tracert netlify.com - Check your tokens and rate limits. An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down.
- Restart the router and the device. Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service.
- Flush the DNS cache. Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again.
ipconfig /flushdns - Turn off VPN and proxy for a moment. VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set.
- Change the DNS server. If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.
Recent incidents
from the official feed, read 21 min agoBetween 13:16 and 13:24 UTC some requests to sites that use Edge Functions experienced increased latency and an elevated rate of 502 errors. This incident has been resolved.
Between 19:05 and 19:18 UTC, some requests to the AI Gateway returned errors. We've since increased the capacity of the affected service, and error rates returned to normal levels at 19:18 UTC. We apologize for the disruption.
This incident has been resolved. Sites on our High-Performance Edge Network have returned to normal operation. The incident began at 12:19 UTC and service was restored at 13:14 UTC.
This incident has been resolved. Sites on the High-Performance Edge have returned to normal operation, and we are no longer seeing elevated error rates.
This incident has been resolved. Service has returned to normal operation, and we are no longer seeing elevated error rates.
The issue causing elevated CDN errors has been resolved. DNS resolution has recovered, and affected services are operating normally.
Questions and experiences
Ask about this page: members and our editors answer. Reading is open; writing needs a free account.
…