Increased error rate in Workflow Operations
ЗакончилосьThis incident has been resolved.
Массовых сбоев с 18 октября, 23:00 по 24 октября, 21:36 не было.
Все 530 сайтов · доступность сайтов с 18 октября, 23:00 по 24 октября, 21:36.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Due to unexpected prefix withdrawals on peering links in IAD and CMH (Ashburn, Virginia and Columbus, Ohio, in the United States) on an external provider, customers experienced increased latency and timeouts from 08:00 to 08:50 UTC. Services have fully normalized following the restoration of prefix advertisements.
This incident has been resolved.
Between 12:58 and 13:03 UTC, Cloudflare experienced an elevated rate of HTTP 5xx errors in Ashburn (IAD).
This incident has been resolved.
This incident has been resolved.
Cloudflare investigated and resolved issues with network performance in Bangkok, Thailand. There may have been elevated response times and an increase in 5xx errors between 06:48 and 07:30 UTC. This has been resolved and normal operations have resumed.
Between 01:13 AM and 02:11 AM UTC, network performance at our ICN-A colo in Seoul was impacted. Users downstream of KINX may have experienced increased latency (TTFB) and elevated Network Error Logging (NEL) metrics due to network path congestion. Performance metrics have since returned to normal baselines, and the issue is now fully resolved.
Workers Cron Triggers have stabilized
This incident has been resolved.
Cloudflare resolved an incident where we observed network performance issues in our Kuala Lumpur (KUL) facility. Customers may have observed elevated error rates and/or increased latency today, 2026-10-15, between approximately 16:10 and 16:15 UTC.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Cloudflare is aware of, and has resolved, an increased level of HTTP errors in London (LHR), between 07:43 UTC and 07:51 UTC. Services have resumed normal operation after this time.
Workers Cron Trigger backlogs have cleared and appear healthy. Cron Trigger schedules should be executing as expected. Some schedule redeploys may be required for a small fraction of Workers who were impacted during the incident.
Customers reaching Los Angeles (LAX) colo may have seen an elevate number of errors during the time. The problem has been mitigated, and we are currently monitoring.
For about 30 minutes there was reduced availability for customers using the OBS API. This has been identified, and we are back to normal for now.
Cloudflare saw issues with network performance in IAD that resulted in an increase in errors across Cloudflare services. Users may have experienced increases errors or timeouts reaching Cloudflare’s network or services.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Каждый сайт открываем из России так же, как браузер посетителя. «Не открывается» — когда три проверки подряд кончились одним из исходов: нет ответа за 10 секунд, ошибка сервера, недействительный сертификат или страница «технические работы» вместо сайта. Защиту от ботов и запрет для роботов сбоем не считаем. Сайт, который не открывается из России, но открывается из-за рубежа, считаем отдельно. Площадка — сеть, через которую сайт отвечает: хостинг, защита от атак или собственная сеть компании. Видите ошибку — напишите нам, перепроверим.
Пришлём письмо через минуты после падения.
Сайт использует cookie. Обязательные нужны для входа, проверки и оплаты. С вашего согласия мы ещё запоминаем, какие страницы вы открыли и что нажали, — но не то, что вы вводите в поля. Сторонние сервисы (Яндекс Метрика) включаются тоже только с вашего согласия: считают посещаемость и записывают, как посетитель пользуется страницей (Вебвизор). Отозвать согласие можно в любой момент. Подробнее — в разделе про cookie.