Customers using BYOIP can have issues updating their BGP prefixes, including advertising or withdrawing prefixes.
Sep 24, 10:22 UTCSep 24, 10:25 UTC
Duration
3m
Impact
Minor
Root cause
Not disclosed
Cloudflare, 90 days
56 incidents
Affected
Bring Your Own IP (BYOIP)Cloudflare Sites and Services - Bring Your Own IP (BYOIP)
Final update
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.
Timeline
- Resolved · Sep 24, 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.
- Investigating · Sep 24, 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.
More from Cloudflare
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2500:03 UTC | Issues with Durable Objects | minor | Ongoing |
| Sep 2420:40 UTC | Intermittent 500 errors for backend services on Replicate | minor | 1h 54m |
| Sep 2417:33 UTC | Delays Starting Cloudflare Workers Builds | minor | 3h 19m |
| Sep 2417:26 UTC | Browser isolation session data sync issues | minor | 5h 11m |
| Sep 2415:20 UTC | Cloudflare Access updates delayed | minor | 3h 5m |
| Sep 2318:42 UTC | Network Performance Degradation , Asia-Pacific | minor | Ongoing |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.