All Systems Operational

About This Site

For more information on how we use this page and what these components mean, please see https://answers.netlify.com/t/important-is-netlify-down-keeping-up-with-netlify-status/35476

High-Performance Edge Network Operational
90 days ago
100.0 % uptime
Today
Standard Edge Network Operational
Origin Servers Operational
Build Pipeline Operational
Netlify Application UI Operational
API Operational
Hosted DNS Operational
Prerendering Operational
Identity Operational
Netlify Functions Operational
Analytics Operational
Log Drains Operational
Collaborative Deploy Previews Operational
Git Gateway Operational
Edge Functions Operational
Netlify Image CDN Operational
Netlify Blobs Operational
Netlify Observability Operational
Netlify Connect Operational
Netlify Create API Operational
Visual Editor Operational
Netlify Forms Operational
Netlify Support Forums Operational
Netlify Helpdesk Operational
Domain Purchasing Operational
Third-Party Services Operational
Atlassian Bitbucket API Operational
Atlassian Bitbucket Webhooks Operational
Atlassian Bitbucket SSH Operational
npm, Inc. Registry Reads Operational
GitHub API Requests Operational
GitHub Webhooks Operational
GitHub Git Operations Operational
NS1 API Operational
NS1 Management Portal Operational
Name.com Operational
Billing Operational
90 days ago
100.0 % uptime
Today
Agent Runners Operational
90 days ago
99.89 % uptime
Today
AI Gateway Operational
Live Tunnel Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
May 20, 2026

No incidents reported today.

May 19, 2026
Resolved - This incident has been resolved. The issue that was causing elevated errors, increased latency, and intermittent site availability across Netlify services has been mitigated. All services, including site delivery and the build pipeline, are now operating normally. We monitored system stability following recovery and are no longer observing elevated error rates or degraded performance
May 19, 23:04 UTC
Monitoring - We have implemented mitigation steps for the issue that was causing elevated errors, increased latency, and intermittent site availability issues across Netlify services. Service health has significantly improved, and core functionality such as site loading and build processing is operating normally for most customers. However, we are continuing to monitor closely to ensure full stability and to catch any residual impact
May 19, 22:14 UTC
Update - We are continuing to investigate an ongoing incident causing elevated latency, errors, and intermittent failures across multiple Netlify services. Impact remains broad and includes intermittent site availability issues where some customer sites may be unavailable or returning errors, as well as disruptions to the build pipeline where builds may fail to start or be delayed
May 19, 21:52 UTC
Update - We are continuing to investigate this issue.
May 19, 21:45 UTC
Update - We are continuing to investigate an ongoing incident causing elevated latency, errors, and intermittent failures across multiple Netlify services. In addition to earlier impact, we are now observing issues with the build pipeline where new builds are not starting for some customers. This may result in delayed or failed deploys, in addition to degraded site performance and intermittent timeouts.
May 19, 21:33 UTC
Investigating - 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.
May 19, 21:08 UTC
Resolved - This incident has been resolved.
May 19, 20:41 UTC
Monitoring - We have resolved the issue causing elevated error rates in the Create API. Systems are now recovering, and we are monitoring closely.
May 19, 20:23 UTC
Investigating - 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
May 19, 18:18 UTC
Resolved - 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
May 19, 17:30 UTC
Resolved - The incident with performance degradation for create.netlify.com has be resolved.
May 19, 14:52 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 19, 14:37 UTC
Identified - The issue has been identified and a fix is being implemented.
May 19, 14:31 UTC
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.
May 19, 14:26 UTC
May 18, 2026

No incidents reported.

May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026
Resolved - This incident has been resolved.
May 15, 18:58 UTC
Monitoring - A fix has been implemented, and we are monitoring the results.
May 15, 17:44 UTC
Identified - We are currently experiencing a delay in cache purges, and some sites on our Standard Edge Network may be serving stale content. The issue has been identified and a fix is being implemented.
May 15, 16:23 UTC
May 14, 2026

No incidents reported.

May 13, 2026

No incidents reported.

May 12, 2026
Resolved - This incident has been resolved.
May 12, 15:38 UTC
Monitoring - We have implemented a fix and are monitoring system performance to ensure services continue to recover as expected.
May 12, 15:20 UTC
Investigating - We are currently investigating increased latency affecting our API and build systems. Some users may experience slower-than-normal response times for API requests and builds while we work to identify the source of the issue.
May 12, 14:30 UTC
May 11, 2026
Resolved - This incident has been resolved.
May 11, 15:27 UTC
Update - We are continuing to monitor for any further issues.
May 11, 15:19 UTC
Monitoring - We are monitoring the results of our fix.
May 11, 14:47 UTC
Identified - We have identified other causes of this latency, and are continuing to work on resolutions.
May 11, 14:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 11, 13:47 UTC
Investigating - We are currently experiencing increased latency in our API and builds. We are investigating the source.
May 11, 13:36 UTC
Resolved - This incident has been resolved.
May 11, 15:27 UTC
Update - We are continuing to monitor for any further issues.
May 11, 15:20 UTC
Monitoring - We are monitoring improvements.
May 11, 14:47 UTC
Identified - The issue has been identified and posted on Github's status page.
May 11, 14:35 UTC
Investigating - We are experiencing issues with our build pipeline due to degraded performance in Github
May 11, 14:31 UTC
May 10, 2026
Resolved - Our network experienced degraded service in the IAD region between 12:53 UTC and 13:53 UTC. This issue is now resolved.
May 10, 16:33 UTC
Resolved - This incident has been resolved.
May 10, 08:56 UTC
Update - We are continuing to monitor for any further issues.
May 10, 08:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 10, 08:32 UTC
Identified - We're experiencing an increase in DNS resolution errors impacting domains on our Standard Edge Network. A fix has been deployed, and we're monitoring the results.
May 10, 08:07 UTC
Resolved - This incident has been resolved.
May 10, 08:21 UTC
Investigating - We are seeing an increase in Agent Runner failures for both initial and follow-up prompts. We are currently investigating this issue.
May 10, 07:15 UTC
May 9, 2026
Resolved - We experienced issues processing account changes between 19:09 and 19:33 UTC. Users may have encountered issues when attempting to use Agent Runners, purchase credits, view credit usage, or complete account transactions. This issue is now resolved.
May 9, 00:58 UTC
May 8, 2026
Resolved - This incident has been resolved.
May 8, 04:00 UTC
Investigating - We're seeing an increased level of errors in the IAD region starting around 02:10 UTC for both our Standard and HP Edge Networks due to an upstream issue at AWS: https://health.aws.amazon.com/health/status.
May 8, 02:53 UTC
May 7, 2026

No incidents reported.

May 6, 2026
Resolved - This incident has been resolved.
May 6, 16:49 UTC
Monitoring - We've implemented a fix and have begun to see improvement starting at 15:15 UTC. We're continuing to monitor the results.
May 6, 15:39 UTC
Investigating - We're experiencing elevated errors and latency starting at 15:00 UTC. We are currently investigating this issue.
May 6, 15:29 UTC