We last checked Netlify at 02:15 UTC and it responded normally in 84 ms. Nobody has reported a problem in the last 24 hours.
Netlify problem reports, last 24 hours
Reports from visitors per hour, in your local time. When reports rise well above the usual level, Netlify is probably having problems.
Having a problem with Netlify?
Choose what isn't working. Reports are anonymous and help other people see if the problem is widespread.
Most reported problems
Recent reports
- No reports in the last 24 hours.
Our checks of netlify.com
Over the last 7 days we checked netlify.com 2,017 times: 100% of checks succeeded, with an average response time of 114 ms. None of our checks of netlify.com has failed in that time.
Each bar is one hour. Green: every check reached netlify.com. Amber: some failed. Red: all failed. Grey: not checked that hour.
Recent Netlify outages
We haven't recorded any Netlify outages since we started keeping this history on 24 October 2026. We record one when our checks of netlify.com fail for 15 minutes in a row, when problem reports jump well above normal, or when Netlify's official status page reports a major outage.
Times are in UTC. Each entry is a time when our checks failed for at least 15 minutes, problem reports jumped well above normal, or Netlify's status page reported a major outage.
Official Netlify status
View Netlify's status page
What to do if Netlify is not working
- Check Netlify's official status page for incidents limited to a specific region or product.
- Look at the exact HTTP status codes you're getting. 5xx errors point to Netlify; 4xx errors usually point to your request or credentials.
- Retry failed API calls with exponential backoff instead of hammering Netlify during an incident.
- Confirm your API keys, tokens and billing are still valid. Expired cards cause sudden 401/403 errors.
- Test from a different network or region to rule out DNS or ISP routing problems.
- Hold off on deploys and config changes until Netlify reports the incident resolved.
Netlify outage FAQ
Is Netlify down for everyone, or just me?
Look at the status at the top of this page. We connect to netlify.com directly from our servers, so if our check works but Netlify doesn't work for you, the problem is more likely your device, network or account. If our check fails, or reports have jumped in the last hour, Netlify is probably having a wider outage.
Why does this page say Netlify is up when it isn't working for me?
Our check confirms that netlify.com is reachable and responding. An outage can still affect only part of Netlify, such as logging in, the mobile app or a single feature, or only some regions. That's why visitor reports matter: when many people report problems at once, we flag Netlify as having problems even if the website loads.
How often do you check Netlify?
We check Netlify automatically every 5 minutes, and again whenever someone opens this page and our last check is more than a few minutes old. A failed check is retried once before it counts.
How do I report a problem with Netlify?
Use "Report a problem" on this page to tell us what isn't working. Reports are anonymous: we don't store your IP address, only a one-way code that stops the same person reporting many times, plus your country.
