Resolved: The incident has been resolved.
Follow
Netlify Status
@netlifystatus
The platform for modern websites and applications.
for news and updates. answers.netlify.com & netlify.com/support for tech support.
Netlify Status’s Tweets
Monitoring: We’re seeing a decrease in failed builds. The team will continue to monitor.
1
1
Show this thread
Investigating: Investigating: We are investigating an increase in build errors starting at 21:45 UTC.
1
3
Show this thread
Resolved: The issue with upstream provider, Github, has been resolved as of 18:43 UTC.
1
Show this thread
Identified: We are confident this issue is due to upstream provider, Github. We will continue to monitor and will post an update as soon as we know more.
1
2
Show this thread
Investigating: We've identified this issue only impacts deploy previews with Github and not other providers. We are continuing to investigate.
1
1
Show this thread
Investigating: We are investigating reports of builds not building due to git ref does not exist / permission errors
1
4
Show this thread
Resolved: Our Network has fully recovered and no more issues have been experienced.
1
Show this thread
Monitoring: We've mitigated the issue affecting our network at 15:00 UTC. We're monitoring our systems.
1
1
Show this thread
Investigating: We are investigating increased errors and latency in the JFK region on the Standard Edge network, since 12:30 UTC.
1
1
Show this thread
Resolved: Beginning at 16:24 UTC, traffic through Edge Functions was failing due to an upstream issue. This has now been fully resolved and all services are operational.
Show this thread
Monitoring: The team has mitigated the root cause of this issue and continue to monitor to ensure service remains stable.
1
Show this thread
Identified: The team has identified the root cause and are working toward a resolution.
1
Show this thread
Investigating: Our team is seeing increased errors with Edge Functions beginning at 16:24 UTC and are currently investigating
1
Show this thread
Resolved: We’ve isolated this to a single customer, and it’s not impacting other customers.
Show this thread
Investigating: Since 04:30 UTC we’ve been experiencing increased error rates in Serverless functions. The team is investigating.
1
Show this thread
Resolved: No further impact expected; we will continue to monitor, but will mark this incident as resolved.
1
Show this thread
Monitoring: Build logs in our UI have returned to normal behavior and visibility. Some logs may have been lost between approximately 19:35 UTC and 20:55 UTC, and some builds may have failed due to associated network connectivity issu…
1
2
Show this thread
Investigating: Our team is investigating reports of not showing build/deploy logs in our UI.
1
3
Show this thread
Resolved: The incident at GitHub has been resolved with no further impact on our build pipeline. While our team will continue to monitor, we'll mark this incident as resolved.
1
Show this thread
Monitoring: A subset of builds failed in our Build Pipeline between 17:10 and 17:15 UTC. We believe this was related to the incident currently open on GitHub's status page: githubstatus.com/incidents/01g5 and will continue to monitor until t…
1
1
Show this thread
Resolved: Error rates are now normal, sites with Edge Functions should be working as before.
1
Show this thread
Monitoring: The team has deployed a fix and the errors seem to be dropping. We will continue to monitor the situation.
1
2
Show this thread
Identified: We have identified the cause and are working on a resolution.
1
2
Show this thread
Investigating: The team is investigating an increased error rate with sites using Edge Functions.
1
2
Show this thread
Resolved: No more errors were seen since 8:57 UTC. The team will continue to monitor.
Show this thread
Monitoring: The issue has been resolved as of 8:57 UTC. We are monitoring the resolution to confirm there are no further issues.
1
Show this thread
Investigating: We are investigating an increased rate of errors in the build system starting at 8:37 UTC.
1
Show this thread
Resolved: Our team identified and mitigated the root cause of this issue. Our team will continue to monitor
Show this thread
Monitoring: We are continuing to monitor for any further issues.
1
Show this thread
Monitoring: We are continuing to closely monitor the recovery of our build pipeline. Some builds may still be impacted and will need to be re-run if failed.
1
Show this thread
Monitoring: Our system self-recovered and we are currently monitoring our build pipeline recovery.
1
Show this thread
Investigating: We are currently investigating an issue causing some builds to fail.
1
Show this thread
Resolved: Our team identified and mitigated the root cause of this issue. Our team will continue to monitor
Show this thread
Investigating: Our team keeps investigating the issue that caused a banner to be displayed in the Netlify UI indicating the account is past due, and an email requesting to update your payment method.
We are actively investigating the…
1
Show this thread
Investigating: We're continuing to investigate the root cause of this issue but can confirm no sites are affected and accounts have been charged correctly.
1
Show this thread
Investigating: We’re investigating an issue with our payment system that is incorrectly considering accounts as overdue
1
Show this thread
Resolved: Between 19:57 UTC to 20:06 UTC we saw a significant increase in errors for sites using Edge Functions. We have mitigated the underlying issue and Edge Functions are now fully operational as of 20:06 UTC
Resolved: The issue causing increased errors on API requests and uncached CDN content has been resolved. We have ensured that further impact from this issue is prevented.
1
Show this thread
Monitoring: Our teams have deployed a fix and since 13:35 UTC, we are no longer observing increased errors with API requests and uncached CDN. We will continue to monitor.
1
1
Show this thread