Is it down for me?
Testing netlify.com from your device…
Most checked
Not listed? Type its address, like example.com, to check it now.
The official status page reports degraded service. Our last check from one location (UtiBox server · Newark, US) found it answering normally in 110 ms, so the website loads, but parts of Netlify may not be working.
Testing netlify.com from your device…
netlify.com loads, but the official status page reports degraded service. Total time to the final page on our latest check.
Thanks, you said it works
0 answers in the last 24 hours · 0 problem reports
One answer per person, counted for 24 hours.
No answers in the last 24 hours
Only our server so far. The regional checks run when the page opens.
No posts yet. Be the first to say how Netlify is working for you.
Our latest check, step by step. Tap a step to open its full record.
Our main check runs from Newark, US. Run the same test from up to 3 internet providers in another country to see whether netlify.com is blocked or broken there.
Press Ctrl + Shift + R (⌘ + Shift + R on a Mac).
Rules out extensions and stored cookies.
Move from Wi-Fi to mobile data, or the other way round.
Windows: ipconfig /flushdns · macOS: sudo dscacheutil -flushcache
They can block or reroute requests.
A wrong clock breaks secure connections.
| Date | Problem | Duration | Peak reports | Status |
|---|---|---|---|---|
| No confirmed incidents recorded for Netlify. | ||||
What people say about Netlify, in their own words, kept apart from our own checks.
Live counts · real numbers, refreshed with the page
Posts are public after a quick review. Don’t share personal details or links.
No posts yet.
Be the first to say how Netlify is working for you.
No posts of this type yet.
That’s every post from the last 30 days.
One answer per person, counted for 24 hours.
Having one of these? Tap it to start a report.
What Netlify status says about its own service, read from its public status page. A separate signal from our own check and from what people report.
Read from the official feed · the provider last updated it .
What Netlify status reports about Netlify. A site can answer our own check while the provider reports a problem with one of its features, and the other way round.
Status information is provided by the service operator. UtiBox is independent and isn’t affiliated with Netlify. It may not reflect regional or account-specific problems.
Minor impactupdated
We are aware that some Netlify Support email responses to customers using Microsoft 365 and Outlook-hosted mailboxes are experiencing delivery delays. These delays appear to be related to an ongoing Microsoft Exchange Online service disruption, with some messages being temporarily deferred by Microsoft's mail servers. Our Support team continues to process and respond to tickets, but affected customers may experience delays receiving our replies. We are monitoring email delivery and will provide an update as Microsoft's service recovers.
No maintenance is planned for Netlify in the last report we read.
Our first successful read in this window was on 9 Nov 2026.
36 resolved updates since May 2026 · 10 major · last one 4 Nov 2026 (6 min)
“We’ve identified an issue at 16:43 UTC that can cause some builds to fail while functions deploy. These affected builds can fail with a system error during the deploy step. Our team is adding capacity and working on a fix.”
“We are investigating an issue causing delays in build logs appearing in the Netlify UI. Our team is actively investigating and we'll provide updates as we learn more.”
“We are investigating elevated build failures and Agent Runner failures.”
“We have identified an ongoing issue with an upstream service provider that may be contributing to delays in build logs appearing in the Netlify UI. We are in contact with the provider and are continuing to monitor the situation. We will provide further updates as more information becomes available.”
“Edge Functions and Function logs from the period between 13:58–15:35 UTC may be delayed in appearing in the Netlify UI and in log drains. We are working to process the backlog; function and edge function requests are not affected.”
“We are investigating an issue causing delays in build logs appearing in the Netlify UI. Our team is actively investigating and will provide updates as we learn more.”
“We are investigating increased Agent Runner failures. We will share updates as we learn more.”
“We have identified an issue with a third-party service used by our build system. Builds started on or after 21:10 UTC that use the CSP extension may experience increased errors.”
“Between 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.”
“We are investigating reports of errors affecting access to sites on our High-Performance Edge Network. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.”
“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.”
“We are investigating reports of errors affecting access to Netlify-hosted sites. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.”
“We have identified a DNS resolution issue affecting our edge network’s ability to reach some origin servers. Requests to affected sites may fail. Our team is working to restore service.”
“We are investigating reports of errors affecting access to Netlify-hosted sites. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.”
“We are experiencing elevated errors within our Image CDN service starting at 12:37 UTC. We are currently investigating this issue.”
“We experienced increased errors and latency in the IAD region on our regular network between 15:50 and 17:45 UTC. This issue has been resolved.”
“Between 10:32 UTC and 10:36 UTC, we observed an increase in errors affecting traffic on the High Performance Edge Network in the FRA region due to an unexpected increase in traffic. Error rates have since returned to normal.”
“We're experiencing increased latency on a subset of CDN nodes in the IAD region. We are currently investigating this issue.”
“On August 18 between 20:02 and 20:08 UTC, some visitors to Netlify-hosted sites and people using the Netlify dashboard received error pages instead of the content they requested. Normal service was restored at 20:08 UTC. We apologize for the disruption”
“We're currently investigating elevated build errors starting at 8:58 UTC.”
“We are currently investigating an issue where some users are encountering errors when uploading attachments to Agent Runners. We have implemented a fix and are monitoring the results.”
“We're currently monitoring an increase in Edge Function errors related to module loading. These errors would primarily surface during builds, but remote module loading can also impact runtime. We will post updates as more information becomes available.”
“We are currently investigating a connectivity issue affecting customers using Bolt. Some customers may be experiencing errors or degraded performance when attempting to use Bolt at this time.”
“We are aware that requests to claude-fable-5 through Netlify AI Gateway are failing. Anthropic has suspended access to Claude Fable 5, and the model is currently unavailable. https://www.anthropic.com/news/fable-mythos-access”
“We are investigating elevated latency affecting image delivery for some Netlify-hosted sites Some customers may experience slower image load times or intermittent errors when loading images. Our engineering team is actively working to mitigate the issue, and we will provide another update as soon as we have more information.Impact start time: 03:19 AM UTC”
“Our team is investigating an increase in observed error rates affecting a subset of sites that use Edge Functions. Affected sites may see elevated 504 responses or slow page loads beginning at approximately 17:00 UTC. We are actively working to identify the cause and will provide updates here.”
“Between May 29th at 15:30 UTC till June 2 6:08 UTC, we experienced sporadic issues with Blobs in our Sydney region, affecting any Function using Blobs, including the ones that are generated by the framework runtimes. Our team has deployed a fix and the errors have subsided.”
“We are currently experiencing delays in our build pipeline due to a current incident at Github.”
“We are continuing to investigate issues affecting image delivery. Some customers may continue to see slow or failed image requests. We are working to identify the cause and will share more information when available.”
“We are currently investigating an issue affecting outbound email delivery for some Netlify services, including support-related communications. Our team is working with our email provider to restore service as quickly as possible”
“We are currently experiencing an increased level of build failures related to downstream issues with GitHub beginning at 06:00 UTC. Any impacted users can attempt to retry their deploys as a workaround while we continue to investigate this issue.”
“We are investigating elevated latency and errors affecting origin services. This is currently impacting request performance and may result in degraded experience or failures for some users.”
“Between 17:38 and 17:57 UTC, we experienced elevated error rates affecting the Build Pipeline. Some customers may have encountered failed deploys or HTTP 500/503 errors during deployment processing. The systems are recovering and we're continuing to investigate the root cause”
“Investigating: We’re seeing degraded performance with create.netlify.com. Some customers are seeing issues with latency or 500 errors while accessing the create.netlify.com”
“We’re seeing degraded performance with create.netlify.com. Some customers are seeing issues with latency or 500 errors while accessing the create.netlify.com.”
No updates of this kind.
From Netlify status’s public status history. UtiBox keeps the official updates it reads for 180 days.
At our last check from UtiBox server · Newark, US, Netlify was up and answering normally. The official status page reports degraded service on its status page, though, so parts of Netlify may not be working even though the website loads. The page refreshes the check automatically.
The official status page (www.netlifystatus.com) reports “Degraded” for Netlify, with 1 open incident. We read it every few minutes. It’s separate from our own check of the netlify.com website above, so the two can differ.
If it’s up here but not for you, the problem is usually local: your connection, DNS, a browser extension, a VPN or a block on your network. Try the fixes on this page, then the Is It My Internet? check.
Our server requests netlify.com and looks at every layer: DNS, the connection, the TLS certificate, the HTTP answer, redirects and the page content. We also check it from up to 12 locations in other countries, using two free probe networks (Globalping and check-host.net), so a regional outage can show here too.
A result is shared for 60 seconds when the site is up and 30 seconds when it has problems, then checked again. You can refresh it yourself after 30 seconds.
Yes. Use “Alert me when it’s back” and we’ll send one email when our check reaches it again. Guests confirm their address first.
UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.
Keep forms secure (ubsid) and remember that you’ve seen this notice (ub_consent). Things you ask us to remember, like light or dark mode and closed banners, are part of this.
UtiBox is free because of ads. Google AdSense and its partners use cookies to show, limit and measure ads. To change how Google personalises the ads you see, use Google’s My Ad Center. To opt out of personalised ads from many companies, visit aboutads.info or youronlinechoices.eu.
Google Analytics counts visits and shows us which pages and tools people use, so we can improve them. It sets _ga cookies. In the EEA, the UK and Switzerland it stores nothing unless you agree. To opt out on any site, use Google’s opt-out browser add-on. Ahrefs Web Analytics counts visits without cookies: it stores nothing on your device and never keeps your IP address; block analytics.ahrefs.com to opt out. Microsoft Clarity records clicks and scrolling for heatmaps and replays, with the tool area and what you type blanked out; block clarity.ms to opt out.