--- title: 'Cloudflare network connectivity issues in North America, October 23, 2026' url: 'https://securteksecurity.com/outages/cloudflare-network-connectivity-issues-north-america-october-23-2026' markdown: 'https://securteksecurity.com/outages/cloudflare-network-connectivity-issues-north-america-october-23-2026.md' date: '2026-10-23' description: 'Cloudflare reported network connectivity issues affecting services in North America on Friday, October 23, 2026, and listed the incident as Major impact on its status page. Cloudflare said a connectivity provider outage caused network congestion and degraded performance for some customers in North …' taxonomy: category: - Outages --- # [Cloudflare network connectivity issues in North America, October 23, 2026](https://securteksecurity.com/outages/cloudflare-network-connectivity-issues-north-america-october-23-2026) 23rd Oct 2026 Cloudflare reported network connectivity issues affecting services in North America on Friday, October 23, 2026, and listed the incident as Major impact on its status page. Cloudflare said a connectivity provider outage caused network congestion and degraded performance for some customers in North America. Downstream providers reported customer impact of their own during the same window, including Pipedrive for US customers, BOSSDesk for East Coast customers, and Ashby, which said access appeared to be recovering. After a fix was implemented and Cloudflare moved the incident to Monitoring, the infrastructure provider failure recurred, and Cloudflare returned to traffic management and traffic engineering work; a downstream provider, Warrant, reported intermittent service interruptions related to its cloud infrastructure provider in that recurrence window. Cloudflare later moved the incident back to Monitoring after rerouting traffic around the impacted paths, and then marked the incident Resolved. Timeline: Cloudflare opened the incident on October 23, 2026 at 15:47 UTC, which is 11:47 AM Eastern. At that point Cloudflare said it was investigating degraded network performance affecting some traffic between its Ashburn and Atlanta data centers, and that some customers might see increased latency, packet loss, or intermittent errors on Workers and other services in the Eastern US. At 16:07 UTC, 12:07 PM Eastern, Cloudflare said it had identified a connectivity provider outage causing network congestion and degraded performance for some customers in North America, that affected customers might experience increased latency, packet loss, and intermittent errors across multiple services, and that its network team was rerouting traffic away from affected paths and working directly with the provider on restoration. At 16:27 UTC, 12:27 PM Eastern, Cloudflare said a fix had been implemented and it was monitoring the results. At 16:59 UTC, 12:59 PM Eastern, Cloudflare said it was continuing to work on a fix for the issue. At 17:03 UTC, 1:03 PM Eastern, Cloudflare said the infrastructure provider had experienced a recurrence of the failure and that it was continuing to apply traffic management actions to further remediate the issue. At 17:33 UTC, 1:33 PM Eastern, Cloudflare said its team was continuing to perform traffic engineering actions to route around impacted paths and would continue performing those actions until all packet drops are mitigated. At 18:18 UTC, 2:18 PM Eastern, Cloudflare moved the incident back to Monitoring and said its network team had rerouted traffic around the impacted paths and was no longer seeing packet drops, that its connectivity provider reported its service had been restored, but that some links were still being brought back, so Cloudflare was keeping its traffic management changes in place. At 18:43 UTC, 2:43 PM Eastern, Cloudflare marked the incident Resolved and said, "This incident has been resolved." The incident page was last updated at 18:43 UTC, 2:43 PM Eastern. Total duration on Cloudflare's record: 2 hours 56 minutes, from 15:47 UTC to 18:43 UTC. Cloudflare status times are published in UTC; Eastern times above are conversions of those published times. Affected services and regions: Cloudflare network services in North America, initially described as traffic between the Ashburn, Virginia and Atlanta, Georgia data centers and services in the Eastern US, then described more broadly as some customers in North America across multiple services. Cloudflare named Workers as an example service in its first update. Downstream impact in the recurrence window: Warrant opened an incident at 17:25 UTC, 1:25 PM Eastern, reporting intermittent service interruptions related to one of its cloud infrastructure providers, with some users potentially experiencing temporary issues accessing certain services, and pointing readers to the Cloudflare status page; Warrant marked its own incident resolved after 19 minutes, at 17:44 UTC, 1:44 PM Eastern. A separate concurrent Cloudflare incident, delayed, missed, and duplicated Workers Cron Triggers, detected at 15:27 UTC on October 23, was listed as ongoing by IsDown, which mirrors the Cloudflare status record; no independent downstream report confirming material customer impact for the Cron Triggers item alone was found, so it is noted here as concurrent context and is not counted as a separate board incident. Provider's account: Cloudflare attributed the incident to a connectivity provider outage, said its network team was rerouting traffic away from affected paths and working directly with the provider on restoration, and then said a fix had been implemented and it was monitoring. Cloudflare later said the infrastructure provider had experienced a recurrence of the failure, that it was continuing traffic management actions, and that its team would continue traffic engineering actions until all packet drops are mitigated. Cloudflare then said traffic had been rerouted around the impacted paths, packet drops were no longer being seen, and the connectivity provider reported its service restored, with some links still being brought back. Cloudflare's closing entry states only that the incident has been resolved. No cause beyond the connectivity provider outage and its recurrence has been published, no indication of a cyberattack has been reported, and no compensation has been stated. Status: Restored at October 23, 2026, 2:43 PM Eastern (18:43 UTC), per Cloudflare's Resolved entry. The incident regressed from Monitoring (fix implemented at 12:27 PM Eastern) after the provider failure recurred at 1:03 PM Eastern, returned to Monitoring at 2:18 PM Eastern with packet drops no longer seen, and was resolved at 2:43 PM Eastern. Duration 2 hours 56 minutes. Sources: [Cloudflare status incident](https://www.cloudflarestatus.com/incidents/sufgcbe8rrwt), [Cloudflare status](https://www.cloudflarestatus.com/), [IsDown Cloudflare status](https://isdown.app/status/cloudflare), [Pipedrive incident report via Pingoru](https://pingoru.io/providers/pipedrive/incidents/12437098), [BOSSDesk incident report via Pingoru](https://pingoru.io/providers/bossdesk/incidents/12437073), [Warrant incident report via Pingoru](https://pingoru.io/providers/warrant/incidents/12437320) --- ## Navigation - Parent: [Outages](https://securteksecurity.com/outages.md) - Next: [DeepSeek outage, October 15, 2026](https://securteksecurity.com/outages/deepseek-outage-october-15-2026.md)