Cloudflare Outage History

Cloudflare major outage View live status →

Pingoru has recorded 622 incidents for Cloudflare: 618 in the last 12 months and 260 in the last 90 days.

Source: cloudflarestatus.com · Aggregated across Cloudflare products

622incidents recorded
618last 12 months
260last 90 days
11 hourstypical duration
Incidents per month
050100AprMayJunJulAugSepOct73
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct62%
Pingoru began tracking Cloudflare in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202690293 of 720 (41%)
May 202686587 of 744 (79%)
June 202689509 of 720 (71%)
July 202695236 of 744 (32%)
August 202678249 of 744 (33%)
September 202692720 of 720 (100%)
October 202673368 of 592 (62%)

Incidents, newest first

Major May 28, 2026 Cloudflare Tunnel Connectivity Issues via Anchorage (ANC) from 2026-05-14 to 2026-05-28 5m Anchorage, AK, United States - (ANC), Tunnel

Started May 28, 2026, 12:13 PM UTC· resolved May 28, 2026, 12:18 PM UTC

  1. monitoring May 28, 2026, 12:13 PM UTC

    Between May 14th and May 28th, 2026, an issue with network routing impacted a subset of Cloudflare Tunnel connections routing through our Anchorage, AK (ANC) point of presence. This issue has been fully mitigated by rerouting traffic to the nearest healthy data centers, and all services are now operating normally. During this time frame, customers with traffic routing through Anchorage may have experienced intermittent or persistent connection failures, manifesting primarily as HTTP 522 errors or connection timeouts. This problem specifically impacted Cloudflare Tunnels routing back to origin servers via this path. Because internal path-optimization systems incorrectly perceived the degraded path as functional, automated failover did not immediately trigger for this specific traffic profile. Traffic routing through all other Cloudflare regions remained entirely unaffected. We sincerely apologize for the duration of this disruption and the impact on our customers. We are actively prioritizing updates to our automated detection and mitigation systems to ensure similar infrastructure and transit anomalies are automatically identified and mitigated moving forward.

  2. resolved May 28, 2026, 12:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 28, 2026 Elevated number of 5xx errors in Dallas Texas –

Started May 28, 2026, 01:00 AM UTC· resolved May 28, 2026, 01:00 AM UTC

  1. resolved May 28, 2026, 01:52 AM UTC

    Between 01:17 UTC - 01:28 UTC, customers reaching Dallas Texas region would have experienced an elevated number of 5xx errors. This incident is now resolved

Read the full incident report →

Notice May 27, 2026 Container Registry Unavailability –

Started May 27, 2026, 09:30 PM UTC· resolved May 27, 2026, 09:30 PM UTC

  1. resolved May 27, 2026, 09:53 PM UTC

    Customers might have seen intermittent unavailability with the container managed registry

Read the full incident report →

Minor May 27, 2026 Cloudflare Analytics availability degraded 6h 1m Analytics

Started May 27, 2026, 11:14 AM UTC· resolved May 27, 2026, 05:15 PM UTC

  1. investigating May 27, 2026, 11:14 AM UTC

    Cloudflare Analytics is degraded and customers might experience elevated rate of errors, and or increased latency while reading data via Cloudflare API.

  2. identified May 27, 2026, 11:36 AM UTC

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

  3. monitoring May 27, 2026, 03:28 PM UTC

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

  4. resolved May 27, 2026, 05:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 26, 2026 AI Gateway Prompts not scanned for DLP 21m AI Gateway

Started May 26, 2026, 07:31 PM UTC· resolved May 26, 2026, 07:52 PM UTC

  1. investigating May 26, 2026, 07:31 PM UTC

    Cloudflare is investigating issues about not correctly scanning certain AI gateway prompts for DLP

  2. resolved May 26, 2026, 07:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 25, 2026 Slow build start time in Workers Builds 1h 9m Workers Builds

Started May 25, 2026, 04:05 PM UTC· resolved May 25, 2026, 05:14 PM UTC

  1. investigating May 25, 2026, 04:05 PM UTC

    Workers Builds are experiencing increased queue times. We are working to analyse and mitigate this problem. More updates to follow shortly.

  2. identified May 25, 2026, 04:36 PM UTC

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

  3. monitoring May 25, 2026, 04:44 PM UTC

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

  4. resolved May 25, 2026, 05:14 PM UTC

    This incident has been resolved. Customers with builds that timed out can retry their build in the Dashboard

Read the full incident report →

Minor May 23, 2026 API Errors 1d API

Started May 23, 2026, 07:41 PM UTC· resolved May 24, 2026, 08:30 PM UTC

  1. investigating May 23, 2026, 07:41 PM UTC

    We are investigating elevated error rates for API requests. Customers may experience failures when making API calls.

  2. monitoring May 23, 2026, 08:57 PM UTC

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

  3. resolved May 24, 2026, 08:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 23, 2026 Cloudflare Zero Trust Gateway Issues — FedRAMP High 12m Zero Trust

Started May 23, 2026, 07:25 PM UTC· resolved May 23, 2026, 07:37 PM UTC

  1. investigating May 23, 2026, 07:25 PM UTC

    Cloudflare is investigating issues with the DNS resolver component within Gateway for customers in the FedRAMP High environment. Affected customers using WARP may experience DNS lookup failures and be unable to reach sites through Gateway. This issue is limited to the FedRAMP High environment and does not affect commercial Cloudflare Gateway customers. We are working to mitigate this problem. More updates to follow shortly.

  2. identified May 23, 2026, 07:29 PM UTC

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

  3. monitoring May 23, 2026, 07:35 PM UTC

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

  4. resolved May 23, 2026, 07:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 22, 2026 Worker Pages Post-Deployment Errors 1h 45m Pages

Started May 22, 2026, 07:10 PM UTC· resolved May 22, 2026, 08:55 PM UTC

  1. investigating May 22, 2026, 07:10 PM UTC

    We are investigating an issue where some customers are experiencing 5xx errors after a Pages deployment completes.

  2. identified May 22, 2026, 07:58 PM UTC

    Issue has been identified, a fix is being implemented.

  3. monitoring May 22, 2026, 08:49 PM UTC

    A fix has been released customer experiencing 5xx errors on their pages deployments should redeploy to resolve.

  4. resolved May 22, 2026, 08:55 PM UTC

    This incident has been resolved. Customers experiencing 5xx errors with Pages deployments should redeploy to resolve.

Read the full incident report →

Minor May 22, 2026 Cloudflare One DNS issues with .internal zones 14m Cloudflare WAN, Cloudflare One Client

Started May 22, 2026, 07:52 AM UTC· resolved May 22, 2026, 08:06 AM UTC

  1. investigating May 22, 2026, 07:52 AM UTC

    We are investigating issues with Cloudflare One (Client and WAN) where DNS resolutions are failing for .internal zones when they are served by private DNS resolvers reachable via Cloudflare One only.

  2. identified May 22, 2026, 07:52 AM UTC

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

  3. monitoring May 22, 2026, 08:02 AM UTC

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

  4. resolved May 22, 2026, 08:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 22, 2026 Increased HTTP 5xx Errors to us-east-1 from Western North America and Asia Pacific co-locations. –

Started May 22, 2026, 04:08 AM UTC· resolved May 22, 2026, 04:08 AM UTC

  1. resolved May 22, 2026, 05:07 AM UTC

    Cloudflare is investigating an increased level of HTTP 5xx errors in us-east-1. We are working to analyse and mitigate this problem. More updates to follow shortly.

Read the full incident report →

Minor May 21, 2026 Prediction and Training status updates delayed – Replicate

Started May 21, 2026, 11:28 PM UTC· resolved May 21, 2026, 11:28 PM UTC

  1. identified May 21, 2026, 09:38 PM UTC

    Our message queues for prediction and training status updates are hitting capacity limits which are causing connection failures for queue consumers. We are in the process of bringing additional capacity online.

  2. resolved May 21, 2026, 11:28 PM UTC

    Message flows are healthy.

Read the full incident report →

Minor May 21, 2026 Constrained H100 capacity – Replicate

Started May 21, 2026, 10:05 PM UTC· resolved May 21, 2026, 10:05 PM UTC

  1. identified May 21, 2026, 03:09 PM UTC

    We are seeing heightened demand for H100 hardware which is causing severe queue delays.

  2. resolved May 21, 2026, 10:05 PM UTC

    H100 hardware contention has resolved. Thank you for your patience!

Read the full incident report →

Minor May 21, 2026 Cloudflare Containers Issues 1h 5m Containers

Started May 21, 2026, 02:38 PM UTC· resolved May 21, 2026, 03:43 PM UTC

  1. investigating May 21, 2026, 02:38 PM UTC

    Cloudflare is investigating issues with starting new containers. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.

  2. resolved May 21, 2026, 03:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 21, 2026 Increased 5XX errors in Porto Alegre and Curitiba, Brazil –

Started May 21, 2026, 07:27 AM UTC· resolved May 21, 2026, 07:27 AM UTC

  1. resolved May 21, 2026, 07:27 AM UTC

    Cloudflare saw an Increased 5XX errors in Porto Alegre and Curitiba, Brazil from 06:28 AM - 07:02 AM UTC. Issue has now been resolved

Read the full incident report →

Minor May 20, 2026 Cloudflare Access delayed audit logs 2h 12m Access

Started May 20, 2026, 07:40 PM UTC· resolved May 20, 2026, 09:52 PM UTC

  1. identified May 20, 2026, 07:40 PM UTC

    An issue with delay audit logs for Access has been identified. A fix is being prepared to resolve the delayed logs.

  2. monitoring May 20, 2026, 07:47 PM UTC

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

  3. resolved May 20, 2026, 09:52 PM UTC

    new audit logs are processing as expected

Read the full incident report →

Minor May 20, 2026 Workers subrequests returning 1006 2h 20m Workers

Started May 20, 2026, 05:19 PM UTC· resolved May 20, 2026, 07:40 PM UTC

  1. investigating May 20, 2026, 05:19 PM UTC

    Cloudflare is aware of and investigating customer reports of some Workers subrequests returning 1006 errors. We are working to analyse and mitigate this problem. More updates to follow shortly.

  2. identified May 20, 2026, 05:21 PM UTC

    We have identified the problem and working to resolve.

  3. monitoring May 20, 2026, 07:12 PM UTC

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

  4. monitoring May 20, 2026, 07:13 PM UTC

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

  5. resolved May 20, 2026, 07:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026 Elevated number of 520 errors in Europe region –

Started May 20, 2026, 03:00 PM UTC· resolved May 20, 2026, 03:00 PM UTC

  1. resolved May 20, 2026, 07:53 PM UTC

    Between 15:00-15:20 UTC Customer traffic in Europe region may have experienced an increased rate of 520 errors

Read the full incident report →

Major May 20, 2026 Increased HTTP 502 Errors in Buenos Aires 18h 43m Buenos Aires, Argentina - (EZE)

Started May 20, 2026, 01:06 PM UTC· resolved May 21, 2026, 07:49 AM UTC

  1. investigating May 20, 2026, 01:06 PM UTC

    Cloudflare is investigating an increased level of HTTP 502 errors in Buenos Aires. We are working to analyse and mitigate this problem. More updates to follow shortly.

  2. monitoring May 20, 2026, 01:57 PM UTC

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

  3. resolved May 21, 2026, 07:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2026 Cloudflare Access AI control - MCP server creation impacted 1h 37m Access, MCP Portal

Started May 19, 2026, 09:59 PM UTC· resolved May 19, 2026, 11:37 PM UTC

  1. investigating May 19, 2026, 09:59 PM UTC

    Customers may experience issue adding new MCP Servers or authenticating existing ones through the Zero Trust Dash

  2. investigating May 19, 2026, 10:09 PM UTC

    We are continuing to investigate this issue.

  3. resolved May 19, 2026, 11:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2026 Intermittent Cloudflare Dashboard SSO login failures with Okta 54m Dashboard

Started May 19, 2026, 07:16 PM UTC· resolved May 19, 2026, 08:10 PM UTC

  1. investigating May 19, 2026, 07:16 PM UTC

    Cloudflare is investigating reports of intermittent authentication failures when logging into the Cloudflare Dashboard using SSO with Okta as the identity provider. Affected users may see a "failed to fetch" error during the login process. Dashboard access via other identity providers and direct username/password login are not currently reported as affected. Cloudflare Access application authentication is not currently reported as affected. Cloudflare Engineering is actively investigating the issue and will provide updates as more information becomes available.

  2. resolved May 19, 2026, 08:10 PM UTC

    Cloudflare engineering has ruled out any service degrading within Cloudflare systems. Customers are advised to review their Okta authentication logs for potential errors. A status update will be provided if Cloudflare Engineering determines the specific Okta issue causing impact.

Read the full incident report →

Minor May 19, 2026 Digital Experience in Cloudflare Zero Trust Latency 32m Digital Experience Monitoring (DEX), Zero Trust

Started May 19, 2026, 03:25 PM UTC· resolved May 19, 2026, 03:57 PM UTC

  1. investigating May 19, 2026, 03:25 PM UTC

    Actions related to Digital Experience are delayed, Cloudflare is aware and investigating.

  2. resolved May 19, 2026, 03:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 19, 2026 Workers AI availability issues 58m Workers AI

Started May 19, 2026, 10:56 AM UTC· resolved May 19, 2026, 11:55 AM UTC

  1. investigating May 19, 2026, 10:56 AM UTC

    Cloudflare is investigating availability issues with several workers AI models.

  2. identified May 19, 2026, 11:09 AM UTC

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

  3. monitoring May 19, 2026, 11:35 AM UTC

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

  4. resolved May 19, 2026, 11:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 19, 2026 Degraded latency for Durable Objects and R2 buckets in WNAM 1h 51m Durable Objects, R2

Started May 19, 2026, 08:13 AM UTC· resolved May 19, 2026, 10:05 AM UTC

  1. investigating May 19, 2026, 08:13 AM UTC

    Durable Objects and R2 buckets in our WNAM buckets may see increased latency, reduced throughput and slightly increased error rates.

  2. investigating May 19, 2026, 08:14 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 19, 2026, 08:23 AM UTC

    We are continuing to investigate this issue.

  4. resolved May 19, 2026, 10:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 18, 2026 Remote preview failing on Workers with attached Durable Object –

Started May 18, 2026, 02:00 PM UTC· resolved May 18, 2026, 02:00 PM UTC

  1. resolved May 18, 2026, 08:06 PM UTC

    Cloudflare identified an issue affecting the remote preview feature between 15:00 and 19:46 UTC. Workers configured with both a remote binding and a Durable Object failed to launch, throwing error code 10375.

Read the full incident report →