Routing/Peering Issues to all cloudflare services from AS3320 (munich/germany)
Since the end of April Telekom customers from Germany, mainly Munich area, suffer serious network issues to all cloudflare services during prime-time, which results in high ping, low bandwidth, packet loss.(7pm-12pm CET)
Telekom refuses to acknowledge any wrongdoing and denies creating support tickets about the issue.
Would someone be able to assist me in that matter resolving the issue or identifying the problem?
Could it be related to BGP Route Leaks?
https://radar.cloudflare.com/routing/anomalies/leak-229025
Tracert:
4 Replies
There's been Telekom issues for the last few months, something along the lines of them wanting CF to pay for peering/traffic and routing free plan to the East Coast or through congested links. As you can see in your example, looks like it's going a congested gtt port instead of peering. A BGP Route Leak isn't likely to cause that, they're more about no connectivity/hijacks and such.
There's a bunch of posts on the forums:
https://community.cloudflare.com/t/connection-to-cf-via-german-telekom-is-very-slow/656849/2
https://community.cloudflare.com/t/latency-to-proxied-dns-entries-high-since-2024-01-30t0715cet/608356/13?u=chaika
https://community.cloudflare.com/t/telekom-cloudflare-routing-problem-only-in-munich/659752/12
and apparantly some on telekom's forums too
Yeah I basically browsed through all the forum posts on the cloudflare forums as well the German Telekom forums. Whose responsibility is it to change the routing to a different destination that isn't congested? Could the routing to the congested node be seen as a move by Telekom to sort of blackmail CF into paying for free direct peering?
Could the routing to the congested node be seen as a move by Telekom to sort of blackmail CF into paying for free direct peering?It's what Telekom does to everyone is my understanding pay for paid peering or suffer congensted public internet routing Generally speaking, when it comes to internet routing/bgp, Cloudflare (the destination) has limited control and only really "suggestions" short of asking the ISP directly who to use. They can change who/where they advertize their prefixes but can't force Telekom to take a different route if they force it on their end or force them to peer. At the end of the day Telekom has the final and full control over who their network peers directly to, and which routes they take/how much capacity they pair for
Thank you for the information. Is it possible to request a reverse traceroute from cloudflare to my local IP for troubleshooting issues on the reverse path?