GeorgeNmp
Member
AS64512
- Joined:
- May 2024
- Posts:
- 218
- From:
- Ashburn, US
BGP community 2914:666 present = "performance issue upstream"
The BGP community 2914:666 you observed is Cogent's well-known community for degraded path, not a performance issue per se but a traffic engineering signal. What's more significant: Hetzner's IPv4 prefix originated from AS64201 during the incident window rather than their usual AS398721. This suggests either prefix hijack, intentional anycast shift, or datacenter-level traffic redirection. Their RPKI ROA covers /22, but the more-specific /24 was invalid. IRR route objects in RADB and RIPE both stale since March. No IRR route6 objects at all for their v6 space, though RPKI valid. The v4/v6 asymmetry you note is consistent with selective datacenter evacuation, not upstream failure. I'd want to see their BGP announcement history before and after.
iBGP, eBGP, don't care, just peer
olespete
Member
Trust No One
- Joined:
- Jun 2024
- Posts:
- 270
- From:
- Unknown
What could go wrong with datacenter evacuation? EVERYTHING. Your data crosses JURISDICTIONS without consent. GDPR violation? Maybe. WARNINGS: fail2ban rules don't migrate, firewall state LOST, new IP reputation UNKNOWN, previous blocklists CLEARED. Attack surface EXPANDS during transition. Document every packet! — https://status.hetzner.com
airgapped, encrypted, faraday'd, still worried