История сбоев Cloudflare

1. 12 августа 2026 г. в 15:04 UTCinvestigating

   We are currently investigating an issue where customers that use Spamhaus for additional filtering of email downstream from the Cloudflare Email Security service are rejecting emails from IPs in the 134.195.26.0/23 block. This IP block should be allowed for all customer downstream systems to avoid treating the Email Security service as an originator of mail. We recommend all Cloudflare Email Security customers disable Spamhaus filtering in downstream systems.

2. 12 августа 2026 г. в 15:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 августа 2026 г. в 16:30 UTCinvestigating

   We are continuing to investigate this issue. Customers using O365 will be impacted only if they have not completed the required setup. Please check your setup and ensure the connector includes all egress IPs: https://developers.cloudflare.com/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/m365-email-security-mx/#2-configure-enhanced-filtering

4. 12 августа 2026 г. в 16:48 UTCmonitoring

   All IPs previously listed by Spamhaus are now clean. Monitoring the propagation of that change to downstream systems.

5. 12 августа 2026 г. в 17:23 UTCresolved

   This incident is now resolved.

1. 11 августа 2026 г. в 14:22 UTCinvestigating

   Отчетность и аналитика для узла HttpRequestsAdaptiveGroups задерживается. Мы работаем над смягчением этой проблемы. Больше обновлений, чтобы следовать в ближайшее время.

2. 11 августа 2026 г. в 15:12 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 11 августа 2026 г. в 16:26 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 11 августа 2026 г. в 14:04 UTCresolved

   Cloudflare знает и решил проблему в нашем лондонском центре обработки данных, где некоторое количество трафика могло привести к сокращению подключения в течение короткого времени. Это потенциальное окно воздействия для этого было 12:58 UTC до 13:25 UTC. Нет постоянного воздействия.

Автоматический перевод официального обновления инцидента.

1. 11 августа 2026 г. в 05:22 UTCinvestigating

   Cloudflare is investigating an increase in 5xx errors in Fuzhou and Foshan China. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

2. 11 августа 2026 г. в 05:22 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11 августа 2026 г. в 05:22 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 11 августа 2026 г. в 05:32 UTCresolved

   This incident has been resolved.

1. 11 августа 2026 г. в 04:16 UTCresolved

   Cloudflare observed an increased level of HTTP 5xx errors in Singapore from 03:30 AM - 04:00 AM UTC. The issue is currently resolved.

1. 10 августа 2026 г. в 10:15 UTCinvestigating

   Cloudflare is aware of, and investigating, an issue which potentially impacts multiple users in Tel Aviv that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.

2. 10 августа 2026 г. в 12:03 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 10 августа 2026 г. в 12:03 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 10 августа 2026 г. в 12:19 UTCresolved

   This incident has been resolved.

1. 10 августа 2026 г. в 11:39 UTCresolved

   Cloudflare became aware of a brief period of reduced availability of the Realtimekit API, between the times 11:07 UTC and 11:13 UTC. This issue has recovered, and no further impact expected.

1. 8 августа 2026 г. в 14:26 UTCinvestigating

   Cloudflare is aware of, and investigating a connectivity issue which potentially impacts end-user connectivity in Egypt. More updates to follow shortly.

2. 8 августа 2026 г. в 15:52 UTCidentified

   Cloudflare has identified a connectivity issue affecting access to some websites from certain networks in Egypt. We are working with external parties to restore network availability. More updates will follow.

3. 8 августа 2026 г. в 17:19 UTCresolved

   Cloudflare’s investigation has determined that Cloudflare services are operating normally. The observed connectivity issue is outside Cloudflare’s network, and we have contacted the relevant external network provider.

1. 8 августа 2026 г. в 08:25 UTCinvestigating

   We have lost dark fiber in the Istanbul region, we are working to follow up with our vendors to restore connectivity. More updates to follow shortly.

2. 8 августа 2026 г. в 19:45 UTCresolved

   This incident has been resolved.

1. 7 августа 2026 г. в 18:42 UTCinvestigating

   Cloudflare is aware, and investigating an issue affecting availability in ENAM for a small number of R2 buckets.

2. 7 августа 2026 г. в 22:54 UTCidentified

   We have identified the cause and mitigated further impact. Writes to a small set of buckets in ENAM were impacted between 14:52-17:02 UTC. We are continuing to work to restore normal availability for these buckets.

3. 7 августа 2026 г. в 23:05 UTCidentified

   We are continuing to work on a fix for this issue.

4. 8 августа 2026 г. в 10:52 UTCidentified

   We are continuing to restore availability for impacted R2 buckets in ENAM. Recovery is progressing well, and we will provide status updates as they becomes available

5. 8 августа 2026 г. в 23:28 UTCidentified

   Availability has been restored for nearly all impacted R2 buckets. A small number of objects uploaded through multipart uploads in ENAM between 14:52 and 17:02 UTC on August 7 remain unavailable. We are continuing to restore access and expect to be able to provide another update soon.

6. 9 августа 2026 г. в 02:35 UTCresolved

   Availability has now been fully restored for all impacted R2 buckets, including the remaining objects uploaded through multipart uploads in ENAM.

1. 7 августа 2026 г. в 16:04 UTCinvestigating

   Cloudflare is aware, and investigating reports where a subset of customers are not seeing logs in the Workers Observability dashboard after deploying a new version of a Worker. Affected Workers continue to run and serve traffic normally. Metrics remain available.

2. 7 августа 2026 г. в 17:10 UTCidentified

   We have identified the root cause and reverted the impacted change. However, for the fix to apply to existing Workers utilizing Gradual Deployments, affected Workers must have their deployment traffic percentages adjusted or redeployed. As a workaround, if you are currently impacted, you can immediately resolve the issue for your service by modifying the traffic weights of your Gradual Deployment (for example, shifting your active deployment weights from 50%/50% to 40%/60%, or redeploying your Worker). We are actively working on an automated fix for all remaining affected customers and will provide another update once resolved.

3. 7 августа 2026 г. в 17:42 UTCresolved

   This incident has been resolved.

1. 7 августа 2026 г. в 13:13 UTCmonitoring

   Cloudflare is investigating issues with network performance in Chicago. We are working to analyse and mitigate this problem. More updates to follow shortly.

2. 7 августа 2026 г. в 14:03 UTCresolved

   This incident has been resolved.

1. 5 августа 2026 г. в 15:09 UTCinvestigating

   Cloudflare is investigating issues with configuration changes for Cloudflare Web Analytics and rum beacon not taking effect or showing errors. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

2. 5 августа 2026 г. в 16:57 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 5 августа 2026 г. в 17:12 UTCresolved

   This incident has been resolved.

1. 5 августа 2026 г. в 14:28 UTCinvestigating

   Cloudflare is aware of and investigating an issue whereby customers using Gateway email lists in their DNS policies are not being enforced. No other impact is implied. More updates to follow shortly.

2. 5 августа 2026 г. в 14:28 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 5 августа 2026 г. в 15:24 UTCinvestigating

   We are currently investigating this issue.

4. 5 августа 2026 г. в 15:36 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 5 августа 2026 г. в 16:20 UTCresolved

   This incident has been resolved.

1. 5 августа 2026 г. в 08:02 UTCinvestigating

   Cloudflare изучает проблему, когда загрузка страниц и рабочих активов снижает доступность. Мы работаем над анализом и смягчением этой проблемы. Больше обновлений, чтобы следовать в ближайшее время.

2. 5 августа 2026 г. в 08:15 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 5 августа 2026 г. в 08:26 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 5 августа 2026 г. в 08:42 UTCresolved

   This incident has been resolved.

Автоматический перевод официального обновления инцидента.

1. 5 августа 2026 г. в 04:17 UTCinvestigating

   Cloudflare is investigating an increased Managed Challenge errors for China Network. We are working to analyse and mitigate this problem. More updates to follow shortly.

2. 5 августа 2026 г. в 04:34 UTCinvestigating

   We are continuing to investigate this issue. This may impact customers using China Network outside of China.

3. 5 августа 2026 г. в 04:51 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 5 августа 2026 г. в 05:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 5 августа 2026 г. в 06:06 UTCresolved

   This incident has been resolved.

1. 4 августа 2026 г. в 20:51 UTCinvestigating

   Cloudflare is aware of, and investigating an issue with elevated R2 error rates and latency for R2 buckets located in Oceania

2. 4 августа 2026 г. в 22:14 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 4 августа 2026 г. в 22:58 UTCresolved

   This incident has been resolved.

1. 4 августа 2026 г. в 18:38 UTCinvestigating

   Cloudflare is investigating elevated 502 errors around Singapore, Jakarta and Bangkok. Further detail will be provided as more information becomes available.

2. 4 августа 2026 г. в 19:23 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 4 августа 2026 г. в 19:46 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 4 августа 2026 г. в 19:53 UTCresolved

   This incident has been resolved.

1. 4 августа 2026 г. в 01:56 UTCinvestigating

   Cloudflare известно, что развертывание Рабочих флага совместимости nodejs compat и даты совместимости на или после 2026-08-04 запрещается. Это влияет на работников и работников платформ. Мы работаем над ослаблением этого утверждения. Чтобы избежать этой ошибки, удалите флаг совместимости nodejs compat.

2. 4 августа 2026 г. в 02:30 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

3. 4 августа 2026 г. в 03:03 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 4 августа 2026 г. в 00:58 UTCinvestigating

   Cloudflare изучает проблемы с производительностью сети в Бангалоре, Индия (BLR). Клиенты, направляющиеся через это место, могут столкнуться с ошибками или сбоями в запросе. Мы работаем над анализом и смягчением этой проблемы. Больше обновлений, чтобы следовать в ближайшее время.

2. 4 августа 2026 г. в 00:59 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

3. 4 августа 2026 г. в 01:02 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.