Minor impactResolvedCDN

Cloudflare incident: Customers using BYOIP can have issues updating their BGP prefixes, including advertising or withdrawing prefixes.

Cloudflare reported this minor-impact incident on its official status page on Sep 24, 2026, 10:22 UTC. It was resolved after 3 min.

Right now Cloudflare is operational. Live Cloudflare status →

🔔 Get alerted when Cloudflare has issuesFree · email alerts · no credit card
Sep 24, 2026, 10:22 UTC
started
Sep 24, 2026, 10:25 UTC
resolved
3 min
duration
Minor
impact

Affected components

  • Bring Your Own IP (BYOIP)

Timeline

updates from Cloudflare's status page ↗
  1. resolvedSep 24, 2026, 10:25 UTC

    This incident has now been resolved - Customers with BYOIP addresses were unable to update their BGP prefixes, including advertising or withdrawing prefixes. Customers making changes to their address maps may also have experienced delays.

  2. investigatingSep 24, 2026, 10:22 UTC

    We are currently investigating an issue where customers with BYOIP addresses will be unable to update their BGP prefixes, including advertising or withdrawing prefixes.

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 38 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 28m. See Cloudflare's uptime and incident history

← Previous: Network Performance Degradation — Asia-Pacific (Sep 23, 2026)Next: Cloudflare Access updates delayed (Sep 24, 2026) →
Cloudflare incident on Sep 24, 2026: Customers using BYOIP can have issues updating their BGP prefixes, including advertising or withdrawing prefixes. · APIStatus.watch