Histórico de interrupções do Cloudflare

1. 12 Eost 2026 da 15:04 UTCinvestigating

   Atualmente estamos investigando um problema onde os clientes que usam Spamhaus para filtragem adicional de email a jusante do serviço Cloudflare Email Security estão rejeitando e-mails de IPs no bloco 134.195.26.0/23. Este bloco IP deve ser permitido para todos os sistemas a jusante do cliente para evitar tratar o serviço de Email Security como um originador de correio. Recomendamos que todos os clientes da Cloudflare Email Security desativem a filtragem de Spamhaus em sistemas a jusante.

2. 12 Eost 2026 da 15:07 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 Eost 2026 da 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 Eost 2026 da 16:48 UTCmonitoring

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

5. 12 Eost 2026 da 17:23 UTCresolved

   This incident is now resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Eost 2026 da 14:22 UTCinvestigating

   Relatórios e análises para o nó HttpRequestsAdaptiveGroups está atrasado. Estamos a trabalhar para atenuar este problema. Mais atualizações a seguir em breve.

2. 11 Eost 2026 da 15:12 UTCmonitoring

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

3. 11 Eost 2026 da 16:26 UTCresolved

   This incident has been resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Eost 2026 da 14:04 UTCresolved

   A Cloudflare está ciente e resolveu um problema dentro do nosso datacenter de Londres, onde algum tráfego pode ter visto uma conectividade reduzida por um curto período de tempo. Esta janela de impacto potencial para isso foi 12:58 UTC a 13:25 UTC. Não há impacto contínuo.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Eost 2026 da 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 Eost 2026 da 05:22 UTCidentified

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

3. 11 Eost 2026 da 05:22 UTCmonitoring

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

4. 11 Eost 2026 da 05:32 UTCresolved

   This incident has been resolved.

1. 11 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 12:03 UTCidentified

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

3. 10 Eost 2026 da 12:03 UTCmonitoring

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

4. 10 Eost 2026 da 12:19 UTCresolved

   This incident has been resolved.

1. 10 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 19:45 UTCresolved

   This incident has been resolved.

1. 7 Eost 2026 da 18:42 UTCinvestigating

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

2. 7 Eost 2026 da 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 Eost 2026 da 23:05 UTCidentified

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

4. 8 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 17:42 UTCresolved

   This incident has been resolved.

1. 7 Eost 2026 da 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 Eost 2026 da 14:03 UTCresolved

   This incident has been resolved.

1. 5 Eost 2026 da 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 Eost 2026 da 16:57 UTCmonitoring

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

3. 5 Eost 2026 da 17:12 UTCresolved

   This incident has been resolved.

1. 5 Eost 2026 da 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 Eost 2026 da 14:28 UTCidentified

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

3. 5 Eost 2026 da 15:24 UTCinvestigating

   We are currently investigating this issue.

4. 5 Eost 2026 da 15:36 UTCmonitoring

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

5. 5 Eost 2026 da 16:20 UTCresolved

   This incident has been resolved.

1. 5 Eost 2026 da 08:02 UTCinvestigating

   Cloudflare está investigando um problema onde uploads para Páginas e ativos de trabalhadores reduziram a disponibilidade. Estamos a trabalhar para analisar e mitigar este problema. Mais atualizações a seguir em breve.

2. 5 Eost 2026 da 08:15 UTCidentified

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

3. 5 Eost 2026 da 08:26 UTCmonitoring

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

4. 5 Eost 2026 da 08:42 UTCresolved

   This incident has been resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 5 Eost 2026 da 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 Eost 2026 da 04:34 UTCinvestigating

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

3. 5 Eost 2026 da 04:51 UTCidentified

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

4. 5 Eost 2026 da 05:54 UTCmonitoring

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

5. 5 Eost 2026 da 06:06 UTCresolved

   This incident has been resolved.

1. 4 Eost 2026 da 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 Eost 2026 da 22:14 UTCidentified

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

3. 4 Eost 2026 da 22:58 UTCresolved

   This incident has been resolved.

1. 4 Eost 2026 da 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 Eost 2026 da 19:23 UTCidentified

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

3. 4 Eost 2026 da 19:46 UTCmonitoring

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

4. 4 Eost 2026 da 19:53 UTCresolved

   This incident has been resolved.

1. 4 Eost 2026 da 01:56 UTCinvestigating

   Cloudflare está ciente de que implantar Workers que a bandeira de compatibilidade nodejs compat e uma data de compatibilidade em ou após 2026-08-04 está sendo proibida. Isso está impactando Trabalhadores e Trabalhadores para Plataformas. Estamos a trabalhar para relaxar esta afirmação. Para evitar este erro, remova o flag de compatibilidade nodejs compat do seu Trabalhador.

2. 4 Eost 2026 da 02:30 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 4 Eost 2026 da 03:03 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Eost 2026 da 00:58 UTCinvestigating

   Cloudflare está investigando problemas com o desempenho da rede em Bangalore, Índia (BLR). O roteamento de clientes através deste local pode experimentar erros de solicitação ou falhas. Estamos trabalhando para analisar e mitigar esse problema. Mais atualizações a seguir em breve.

2. 4 Eost 2026 da 00:59 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 4 Eost 2026 da 01:02 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.