Still Bad Routing from DTAG in Germany

I found a topic from Q1/2021 which said CF is working on it and cannot give an ETA. CF did stop routing TATA communications in Frankfurt (AS6453).

Just noticed that I am routed to Paris. Ping is >50ms to 1.1.1.1, 8.8.8.8 and 9.9.9.9 both responds time is >13ms

@oneandonlyjason did you receive any news via your ticket?
It’s hard to believe, that CF - running one of the largest CDNs in the world - takes months or even has no ETA at all to fix the routing of the biggest ISPs (Deutsche Telekom, Vodafone) in an industry leading nation?!

2 Likes

Hey, because my Ticket got closed after the answer i recieved i didnt get any new Information after this Point.

As far i know Vodafone got fixed after Vodafone migrated the Unitymedia Network. But Telekom still has this Problem

2 Likes

These incumbents, eyeball hostage takers, are the European equivalent of Comcast or Telstra in AUS, they won’t peer domestically or at least not in the same state in the USA, or if they do they’ll keep the capacity deliberately constrained - here’s a 10gig cross connect but we don’t have peering capacity for the other 390gbit of traffic you want to exchange, ultimately they want to CF to purchase paid transit from their edge locations to them - quite often in same building that the peering fabric is in.

3 Likes

I did create ticket #2147404

1 Like

@MoreHelp

1 Like

Darn, @TKlein is from that area, but probably didn’t catch this thread when he was on earlier.

1 Like

Hi there @user6094,

So we have a bit more context, can you please also provide us with the plain text output of the following commands from the device(s) where issues were observed?

nslookup example.com
curl https://example.com/cdn-cgi/trace/
traceroute example.com
mtr example.com

Replace example.com with your site and feel free to send me these details back on the ticket for our analysis. With this, I can loop in someone from our networking team to weigh in on the situation at hand.

Cheers,

5 Likes

I did send the requested output for cloudflare.com and one.one.one.one as I am not a direct customer of yours. I did notice that my local DNS server no longer was using 1.1.1.1 but 8.8.8.8 due to slow response time, so I started analyzing the traffic und digging in the internet :nerd_face:

Pls also look at my images from the initial post in the ticket. The ping times to 1.1.1.1 vary by day time (e.g.11 pm - 11am: 20ms, 11am - 11pm: 40ms), while 8.8.8.8 response constantly at 13ms, no change during day time.

1 Like

Work is being undertaken in Frankfurt, which may cause suboptimal routing for a small subset of end-users.

5 Likes

Any Update on this?
The bad routing from 1.1.1.1 to DTAG is now since over 5 Months…

https://1.1.1.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJObyIsImlzRG9oIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjEuMS4xIjoiWWVzIiwicmVzb2x2ZXJJcC0xLjAuMC4xIjoiWWVzIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTExMSI6Ik5vIiwicmVzb2x2ZXJJcC0yNjA2OjQ3MDA6NDcwMDo6MTAwMSI6Ik5vIiwiZGF0YWNlbnRlckxvY2F0aW9uIjoiQ0RHIiwiaXNXYXJwIjoiTm8iLCJpc3BOYW1lIjoiQ2xvdWRmbGFyZSIsImlzcEFzbiI6IjEzMzM1In0=

Tracepath from DTAG DSL to 1.1.1.1:
1?: [LOCALHOST] pmtu 1492
1: _gateway 4.340ms
1: _gateway 3.614ms
2: *****697.dip0.t-ipconnect.de 9.928ms
3: *****972.dip0.t-ipconnect.de 10.297ms asymm 4
4: 80.156.162.178 13.500ms asymm 8
5: if-ae-54-2.tcore1.fr0-frankfurt.as6453.net 23.524ms asymm 11
6: if-ae-55-2.tcore2.pvu-paris.as6453.net 24.059ms asymm 10
7: if-ae-49-2.tcore1.pvu-paris.as6453.net 43.158ms asymm 9
8: if-ae-11-2.tcore1.pye-paris.as6453.net 21.540ms asymm 7

2 Likes

If DTAG have CF over a barrel, then it’s unlikely you’ll will see to FRA ingestion for Dtag eyeballs on Free/Pro plans, it would simply be too expensive without going to AWS/Azure/GCP per gig pricing. My bet would be CF would say something but is constrained by confidential agreements during and after negotiations. Many transit providers dont have links with DTAG within Germany, but peer with them in nearby countries as a compromise. I recall reading Telia do have in country though, however a bit like bundle merchant account pricing vs interchange++, if CF pushed all their DTAG traffic over Telia then Telia would pull the plug or adjust pricing to reflect that…

Since it looks like 1.1.1.1 isn’t ingesting in FRA then you can probably presume its not even available on the higher plans

5 Likes

If that’s true, that would be very very sad :frowning:

1 Like

FYI
https://one.one.one.one/cdn-cgi/trace/ via IPv6 is answered by OTP
https://1.1.1.1/cdn-cgi/trace/ via IPv4 is answered by CDG

2 Likes

Same problem here.
All websites hosted through Cloudflare are extremely slow …

https://speed.cloudflare.com:


mtr:
629-93-max

1 Like

What makes it even worse is that Telekom routing flaps beween

AS6453 - Paris
AS6453 - Amsterdam
and
AS2914

None of those connections are without packet loss at busy times, pings are especially bad on the paris path.

3 Likes

Quoting from the last reply by CF to my ticket:

Tata is disabled in Frankfurt, and as such, they’ll route to either Amsterdam or Paris.

Tata seems to be load-balancing between Paris and Amsterdam, as they’re roughly equivalent

1 Like

For me even though Cloudflare and m247 have a common ix in Frankfurt, traffic still routes to Paris.

2 Likes

Fun (?) Fact: Today, Routing is via AS6762, Telecom Italia Sparkle.
Actually not that bad, but it is not a busy time right now.

Edit: In the evenning 4% packet loss, same route

4 Likes

I do see this too.
Ping times to 1.1.1.1 dropped from 23ms to 18ms on June 7th and on June 9th they even dropped down to 12ms. That’s quite the response Google DNS has (8.8.8.8, 11ms).

Is it just luck or magic or did somebody alter something on purpose? :slight_smile:

2 Likes

I noticed it too a few Days ago. It seems like they removed Tata which was disabled in the Frankfurt POP and switched to Telecom Italia Sparkle. The AS6762 seems to have a pretty bad Reputation. But it is at least a little little bit faster then to route Everything to Paris (at least for me right now) and the Ping Time is a lot better when stuff is routed over Frankfurt (Before >50ms now 7-10ms)

1 Like