Event Monitor Cyber
EM-20261118-W0I5 OutageMedium severity

Cloudflare: Network Connectivity Drop

Nov 16, 2026 · Provider · reported by Provider status pages (Statuspage), IODA (Georgia Tech)

Share

Providers' own notes put the impact at 20:10–20:40 UTC on Nov 16, 04:50–05:50 UTC on Nov 17, 13:55–14:35 UTC, 02:31–03:04 UTC on Nov 18, 07:00–10:00 UTC.

Status
Resolved

Since : every provider marked it resolved.

First Signal
Nov 16 14:30 UTCC123 Provider status pages (Statuspage)
Page Born
Nov 18 07:20 UTCsecond source joined
Last Signal
Nov 19 08:56 UTC22 hours before snapshot
Sources
21 official · 1 research, news or crowd
Lasted
3 daysfirst signal to resolved

Life Of This Page

  1. 1
    Born
    A second, independent provider or measurement sees it.
  2. 2
    Developing
    Reports and measurements join.
  3. 3
    Confirmed
    A provider status page acknowledges it.
  4. 4
    Resolved · Now
    Every provider marks it resolved and 6 hours pass quietly, or 24 hours pass with no new signal.
  5. 5
    Archived
    Not yet
    30 days after resolved. Read only; the link keeps working. Reopens if it comes back.

The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.

Outage Lifecycle

  1. First Report: reached
    Nov 16 14:30 UTC
    C123 Provider status pages (Statuspage)
  2. Corroborated: reached
    Nov 18 07:20 UTC
    2 independent sources
  3. Acknowledged: reached
    Nov 16 14:30 UTC
    C123 status page
  4. Network Check: not yet
    Not yet
    No network data for this provider
  5. Restored: reached
    Nov 19 08:56 UTC
    All status incidents resolved

Timeline

12:00Nov 1712:00Nov 1812:00Nov 1912:00BornResolvedC123 Provider status pages (StatuspaC111 IODA (Georgia Tech)

Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.

Signals

  1. Cloudflare: Cloudflare Access Issue (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  2. Cloudflare: Cloudflare Access Issue (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  3. Cloudflare: Cloudflare Access Issue (opens source in a new tab) identified. Cloudflare is investigating an issue with Cloudflare Access. A recent Cloudflare Access release removed the sub claim from service token JWTs, which can cause authentication failures for applications that… Med severityProvider StatusC123 Provider status pages (Statuspage)
  4. Cloudflare: Degraded connectivity between Europe and Asia Pacific (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  5. Cloudflare: Degraded connectivity between Europe and Asia Pacific (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  6. Cloudflare: Degraded connectivity between Europe and Asia Pacific (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  7. Cloudflare: Increased latency on Analytics API (GraphQL) queries (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  8. Cloudflare: Degraded connectivity between Europe and Asia Pacific (opens source in a new tab) investigating. Cloudflare is investigating degraded connectivity between Europe and the Asia Pacific region. Customers may experience increased errors and latency for requests traversing this path, including requests… Med severityProvider StatusC123 Provider status pages (Statuspage)
  9. Cloudflare: Increased latency on Analytics API (GraphQL) queries (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  10. Cloudflare: Increased latency on Analytics API (GraphQL) queries (opens source in a new tab) identified. Cloudflare has identified an issue where some customers may experience latency querying the GraphQL API. We are working to analyze and mitigate this problem. More updates to follow shortly. Med severityProvider StatusC123 Provider status pages (Statuspage)
  11. Cloudflare: R2 Downloads Stalling in Japan (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  12. Connectivity drop: AS209242 (CLOUDFLARESPECTRUM) (Cloudflare London, LLC) (opens source in a new tab) 1 IODA alerts in 6 hours (1 critical), signals: bgp. Entity type: asn. Med severityMeasurementC111 IODA (Georgia Tech)
  13. Cloudflare: R2 Downloads Stalling in Japan (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  14. Cloudflare: R2 Downloads Stalling in Japan (opens source in a new tab) investigating. Cloudflare is aware of, and investigating an issue where R2 Downloads are stalling for users connecting via datacenters in Japan. Further detail will be provided as more information becomes available. Med severityProvider StatusC123 Provider status pages (Statuspage)
  15. Cloudflare: Network Performance Issues in North America (opens source in a new tab) resolved. Between approximately 07:00 UTC and 10:00 UTC Cloudflare investigated issues with network performance in North America. This has since been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  16. Cloudflare: Network disruption across multiple colocations in India (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  17. Cloudflare: Network disruption across multiple colocations in India (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  18. Cloudflare: Network disruption across multiple colocations in India (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  19. Cloudflare: Network disruption across multiple colocations in India (opens source in a new tab) investigating. Cloudflare is investigating a network disruption across multiple datacenters in India, impacting some Cloudflare services in region. We are working to analyse and mitigate this problem. More updates to… Med severityProvider StatusC123 Provider status pages (Statuspage)
  20. Connectivity drop: CLOUDFLARENET -- Región Metropolitana de Santiago (Cloudflare, Inc.) (opens source in a new tab) 1 IODA alerts in 6 hours (1 critical), signals: bgp. Entity type: geoasn. Med severityMeasurementC111 IODA (Georgia Tech)
  21. Connectivity drop: CLOUDFLARENET -- Chile (Cloudflare, Inc.) (opens source in a new tab) 1 IODA alerts in 6 hours (1 critical), signals: bgp. Entity type: geoasn. Med severityMeasurementC111 IODA (Georgia Tech)
  22. Cloudflare: Network Performance Issues in Paris (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  23. Cloudflare: Network Performance Issues in Paris (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. This incident impacted Cloudflare Network Interconnect (CNI) only. Med severityProvider StatusC123 Provider status pages (Statuspage)
  24. Cloudflare: Network Performance Issues in Paris (opens source in a new tab) identified. We are continuing to work on a fix for the issue. Med severityProvider StatusC123 Provider status pages (Statuspage)
  25. Cloudflare: Network Performance Issues in Paris (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  26. Cloudflare: Network Performance Issues in Paris (opens source in a new tab) investigating. Cloudflare is investigating issues with Network Performance in Paris, FR. We are working to analyze and mitigate this problem. More updates to follow shortly. Med severityProvider StatusC123 Provider status pages (Statuspage)
  27. Cloudflare: Errors and stalled predictions on some models (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  28. Cloudflare: Elevated 5xx error rates and latency in Mumbai (opens source in a new tab) resolved. Between 02:31-03:04 UTC on November 18, a subset of customers reaching Mumbai, IN, may have experienced an elevated number of 5xx errors and increased latency. This has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  29. Cloudflare: Errors and stalled predictions on some models (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  30. Cloudflare: Cloudflare Access Issue (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  31. Cloudflare: Cloudflare Access Issue (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  32. Cloudflare: Cloudflare Access Issue (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  33. Cloudflare: Cloudflare Access Issue (opens source in a new tab) investigating. Cloudflare is investigating issues with Cloudflare Access. Customers may experience a delay making configuration changes to Access. We are working to understand the full impact and mitigate this problem… Med severityProvider StatusC123 Provider status pages (Statuspage)
  34. Cloudflare: Issues with Durable Objects and Dependent Services (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  35. Cloudflare: R2 elevated errors and timeouts for requests from South America (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  36. Cloudflare: Issues with Durable Objects and Dependent Services (opens source in a new tab) investigating. We are investigating reports of elevated timeout rates and performance degradation affecting Durable Objects. This may impact dependent services, including Stream and Containers. Our team is actively… Med severityProvider StatusC123 Provider status pages (Statuspage)
  37. Cloudflare: Errors and stalled predictions on some models (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Current impact: predictions on OpenAI models are back to normal. Predictions on other models may still return HTTP 500 errors or stay in a… Med severityProvider StatusC123 Provider status pages (Statuspage)
  38. Cloudflare: R2 elevated errors and timeouts for requests from South America (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  39. Cloudflare: R2 elevated errors and timeouts for requests from South America (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  40. Cloudflare: R2 elevated errors and timeouts for requests from South America (opens source in a new tab) investigating. We are investigating elevated errors and read timeouts affecting R2 requests originating from South America (impacting datacenters such as GRU, GIG, EZE, and SCL). Our team is actively working to… Med severityProvider StatusC123 Provider status pages (Statuspage)
  41. Cloudflare: Network performance issues in Los Angeles (LAX) and Frankfurt (FRA) datacenters (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  42. Cloudflare: Network performance issues in Los Angeles (LAX) and Frankfurt (FRA) datacenters (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  43. Cloudflare: Network performance issues in Los Angeles (LAX) and Frankfurt (FRA) datacenters (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  44. Cloudflare: Network performance issues in Los Angeles (LAX) and Frankfurt (FRA) datacenters (opens source in a new tab) investigating. Cloudflare is investigating issues with network performance in Los Angeles (LAX), United States and Frankfurt (FRA), Germany datacenters. We are working to analyse and mitigate this problem. More updates… Med severityProvider StatusC123 Provider status pages (Statuspage)
  45. Cloudflare: Turnstile verification failures (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  46. Cloudflare: Errors and stalled predictions on some models (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Current impact: prediction requests for some models may return HTTP 500 errors, and some predictions may stay in a processing state. Customers… Med severityProvider StatusC123 Provider status pages (Statuspage)
  47. Cloudflare: Errors and stalled predictions on some models (opens source in a new tab) investigating. We are currently investigating this issue. Cloudflare is aware of, and investigating, an issue affecting predictions for some models on Replicate. Customers may see prediction requests return HTTP 500… Med severityProvider StatusC123 Provider status pages (Statuspage)
  48. Cloudflare: Cloudflare One Gateway traffic unable to connect to Cloudflare domains that are regionalized (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  49. Cloudflare: Cloudflare One Gateway traffic unable to connect to Cloudflare domains that are regionalized (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  50. Cloudflare: Elevated number of 5xx and 499 errors (opens source in a new tab) resolved. Between 13:55-14:35 UTC customers reaching Minneapolis, MN and Saint Louis, MO would have experienced an elevated number of 499 and 5xx errors. Med severityProvider StatusC123 Provider status pages (Statuspage)
  51. Cloudflare: Cloudflare One Gateway traffic unable to connect to Cloudflare domains that are regionalized (opens source in a new tab) identified. We are investigating reports of connection drops and TCP resets affecting requests routed through Cloudflare WARP and Gateway that aims for Cloudflare Regional Services hostnames and domains. Engineering… Med severityProvider StatusC123 Provider status pages (Statuspage)
  52. Cloudflare: Turnstile verification failures (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  53. Cloudflare: Turnstile verification failures (opens source in a new tab) investigating. We are investigating reports of Turnstile verification failures affecting some users with browser fingerprinting protection enabled, including Helium. We are assessing the impact and potential mitigations. Med severityProvider StatusC123 Provider status pages (Statuspage)
  54. Cloudflare: Elevated number of 52x origin connectivity errors in Seoul (opens source in a new tab) resolved. Between 04:50 - 05:50 UTC 17th November, customers in Seoul may have experienced an elevated number of 52x origin connectivity errors. This is now resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  55. Cloudflare: Network Performance Issues in Ashburn, US (opens source in a new tab) resolved. This incident has been resolved. Info severityProvider StatusC123 Provider status pages (Statuspage)
  56. Cloudflare: Network Performance Issues in Ashburn, US (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  57. Cloudflare: Network Performance Issues in Ashburn, US (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  58. Cloudflare: Network Performance Issues in Ashburn, US (opens source in a new tab) investigating. Cloudflare is investigating an issue affecting network performance in Ashburn, US has been identified and a fix is being implemented. Customers may experience elevated error rates and increased latency. Med severityProvider StatusC123 Provider status pages (Statuspage)
  59. Cloudflare: Network Performance Issues in Montreal, Canada (opens source in a new tab) resolved. Cloudflare identified an issue that affected network performance in Montreal, Canada, between 20:10 and 20:40 UTC on November 16, 2026. During this time, customers may have experienced increased HTTP 499… Med severityProvider StatusC123 Provider status pages (Statuspage)
  60. Cloudflare: Errors creating predictions for some models (opens source in a new tab) resolved. This incident has been resolved. Med severityProvider StatusC123 Provider status pages (Statuspage)
  61. Cloudflare: Errors creating predictions for some models (opens source in a new tab) monitoring. A fix has been implemented and we are monitoring the results. Med severityProvider StatusC123 Provider status pages (Statuspage)
  62. Cloudflare: Errors creating predictions for some models (opens source in a new tab) identified. The issue has been identified and a fix is being implemented. Med severityProvider StatusC123 Provider status pages (Statuspage)
  63. Cloudflare: Errors creating predictions for some models (opens source in a new tab) investigating. We are currently investigating this issue. Cloudflare is aware of, and investigating, an issue affecting prediction creation for some models on Replicate. Customers may see requests fail with the error… Med severityProvider StatusC123 Provider status pages (Statuspage)