58 Netlify incidents · styczeń 2026 — official updates, affected components, duration and resolution details.
Doświadczyliśmy zwiększonych błędów i opóźnień w regionie IAD w naszej regularnej sieci między 15: 50 a 17: 45 UTC. Kwestia ta została rozwiązana.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Między 10: 32 UTC a 10: 36 UTC, zaobserwowaliśmy wzrost błędów wpływających na ruch w sieci High Performance Edge Network w regionie FRA ze względu na nieoczekiwany wzrost ruchu. Od tego czasu stawki błędów wróciły do normy.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Doświadczamy zwiększonego opóźnienia w podgrupie węzłów CDN w regionie IAD. Obecnie badamy tę kwestię.
Żądanie opóźnienia w całym regionie IAD powróciło do normalnego poziomu i nadal monitorujemy sytuację.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
W dniach 18 sierpnia między 20: 02 a 20: 08 UTC niektórzy odwiedzający strony Netlify- hostowane i osoby korzystające z deski rozdzielczej Netlify otrzymali zamiast żądanych treści strony błędów. Normalna obsługa została przywrócona o 20: 08 UTC. Przepraszamy za zakłócenia
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie badamy podwyższone błędy budowlane zaczynając o 8: 58 UTC.
Od 9: 32 UTC widzimy spadek nieudanego budowania. Zespół będzie monitorował.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie badamy problem, w którym niektórzy użytkownicy napotykają błędy podczas wysyłania załączników do agenta Runnersa. Wprowadziliśmy rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie monitorujemy wzrost błędów funkcji Edge związanych z załadunkiem modułu. Błędy te wynurzyłyby się przede wszystkim podczas budowy, ale zdalne ładowanie modułu może mieć również wpływ na czas pracy. Będziemy publikować aktualizacje w miarę dostępności większej ilości informacji.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
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.
While recovery is in progress, enabling and disabling sites may take longer than usual. Customers using Bolt may continue to experience delays or intermittent errors when accessing, creating, or updating Bolt-powered sites
This incident has been resolved.
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
This incident has been resolved.
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
We are seeing recovery from the elevated latency affecting image delivery for some Netlify-hosted sites across our network. Error rates have decreased and image delivery performance has improved. Our engineering team is continuing to monitor the service to confirm stability. We will provide another update once the issue is fully resolved.
This incident has been resolved.
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.
We have identified an issue with a subset of our Edge Functions infrastructure causing elevated 504 errors for some sites beginning at approximately 17:00 UTC. We are applying mitigations and error rates are improving. Customers do not need to take any action. We will continue to provide updates here.
We have applied a mitigation and error rates for affected sites have returned to normal levels as of approximately 20:30 UTC. We are continuing to monitor the situation and will provide a final update once we have confirmed full recovery
This incident has been resolved. Between approximately 17:00 and 20:30 UTC, a subset of sites using Edge Functions experienced elevated 504 error rates. We applied a mitigation and error rates have remained at normal levels since. We apologize for the impact to your sites and visitors.
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.
In addition to delayed builds, we are also experiencing build failures due to the current incident at Github.
This incident has been resolved, and builds have returned to functioning normally.
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 have implemented a fix and are monitoring results. Some customers may have experienced slow or failed image requests. We will continue to monitor image delivery and provide an update once the issue is fully resolved.
This incident has been resolved.
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
outbound email delivery has been restored and emails are now processing successfully. Some delays may continue while queued messages are delivered. We are continuing to monitor the recovery closely
This incident has been resolved.
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.
This incident has been resolved.
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.
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.
We are continuing to investigate this issue.
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
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
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
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 have resolved the issue causing elevated error rates in the Create API. Systems are now recovering, and we are monitoring closely.
This incident has been 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
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The incident with performance degradation for create.netlify.com has be resolved.