Minor impactResolvedCDN

Cloudflare incident: Increased errors and latency for CNI 2.0 traffic in LAX

Cloudflare reported this minor-impact incident on its official status page on Oct 29, 2026, 06:55 UTC. It was resolved after 1h 33m.

Right now Cloudflare is operational. Live Cloudflare status →

🔔 Get alerted when Cloudflare has issuesFree · email alerts · no credit card
Oct 29, 2026, 06:55 UTC
started
Oct 29, 2026, 08:28 UTC
resolved
1h 33m
duration
Minor
impact

Affected components

  • Cloud Network Interconnect (CNI)
  • Los Angeles, United States - (LAX)

Timeline

updates from Cloudflare's status page ↗
  1. resolvedOct 29, 2026, 08:28 UTC

    This incident has been resolved.

  2. monitoringOct 29, 2026, 08:08 UTC

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

  3. investigatingOct 29, 2026, 06:55 UTC

    Cloudflare is aware of and investigating an issue affecting Cloudflare Network Interconnect (CNI) 2.0 traffic in LAX (Los Angeles). Some CNI 2.0 customers with traffic in this location may observe increased errors and/or latency on their connections.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cloudflare's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cloudflare have incidents?

Cloudflare reported 124 incidents in the last 90 days, 12 of them major or critical. A typical incident lasted 1h 33m. See Cloudflare's uptime and incident history

← Previous: Network Performance Issues in Queretaro, MX (Oct 28, 2026)Next: Increased Worker services errors (Oct 29, 2026) →