- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm using Adguard DNS with anycast IP addresses 94.140.14.14 and 94.140.15.15 however, I'm not getting the best route.
I'm located on the east coast and Adguard has a server in NYC. Despite this, when I'm connected to my Fios network or even my friend's Fios network, I get routed to their European servers.
I was told that Verizon would have to change their BGP roytes for that IP address.
Solved! Go to Correct Answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm seeing the same sort of behavior from Verizon's looking glass server in New York:
traceroute to 94.140.14.14 (94.140.14.14), 30 hops max, 52 byte packets
1 0.ae13.GW14.NYC1.ALTER.NET (140.222.235.127) 0.936 ms 3.878 ms 3.068 ms
2 WS--Vodafone-Group-Services-Limited-Voda.customer.alter.net (204.148.1.254) 3.606 ms 1.264 ms 1.575 ms
3 ae0-xcr1.nyh.cw.net (195.2.25.70) 120.948 ms 122.097 ms 121.095 ms
MPLS Label=396305 CoS=0 TTL=1 S=1
4 et-10-3-0-xcr1.ptl.cw.net (195.2.24.242) 121.696 ms 121.571 ms 122.093 ms
MPLS Label=868061 CoS=0 TTL=1 S=1
5 ae29-xcr1.mlu.cw.net (195.2.24.229) 116.216 ms 116.002 ms 115.970 ms
MPLS Label=747209 CoS=0 TTL=1 S=1
6 ae23.0-xcr1.sof.cw.net (195.2.16.2) 102.332 ms 102.506 ms 102.293 ms
MPLS Label=119872 CoS=0 TTL=1 S=1
7 ae1-xcr1.ise.cw.net (195.2.18.209) 116.043 ms 110.482 ms 115.758 ms
8 cust-gw-ae3-17-xcr1.ise.cw.net (195.2.26.254) 121.584 ms 121.737 ms 116.560 ms
9 213.194.115.38 (213.194.115.38) 114.022 ms 119.523 ms 114.379 ms
10 * * *
11 185.137.215.90 (185.137.215.90) 118.845 ms 113.276 ms 118.553 ms
12 vl203.ist-mars-dist-2.cdn77.com (138.199.0.209) 113.397 ms vl201.ist-mars-dist-1.cdn77.com (138.199.0.207) 118.822 ms 118.674 ms
13 dns.adguard.com (94.140.14.14) 113.581 ms 113.220 ms 113.490 ms
Here's the BGP announcement from the same looking glass:
94.140.14.0/24 (2 entries, 1 announced)
*BGP Preference: 170/-101
Age: 1w3d 19:44:20 Metric: 0 Metric2: 504
Announcement bits (4): 0-KRT 3-RT 9-BGP_RT_Background 10-Resolve tree 4
AS path: 1273 15924 57152 60068 212772 I (Originator)
Communities: 0:201 701
Localpref: 100
BGP Preference: 170/-101
Age: 1w3d 19:44:20 Metric: 0 Metric2: 504
AS path: 1273 15924 57152 60068 212772 I (Originator)
Communities: 0:201 701
Localpref: 100
It appears AdGuard doesn't have transit from Verizon, so the BGP is preferring Vodafone and taking the route to Europe. I found AdGuard's East Coast POP which is hosted out of CDN77's network. On my ISP (Charter) I have to route through Comcast, which is one of CDN77's immediate transit providers. Although Charter has transit to CDN77 directly, my immediate AS heads to Comcast since Comcast is a more preferred peer. The preference is usually based on costs (such as, Comcast provides more bandwidth to CDN77 and for less money, therefore Comcast may be a better choice to direct user traffic through). In this case the cost decisions would be on CDN77, which would be upstream from AdGuard.
A change like this usually needs coordination from Verizon, as well as the intermediate networks to make sure the announcement for the New York Datacenter can get to Verizon on a more preferred path than Vodafone, It may also need to be something AdGuard needs to coordinate since they do have some control over BGP for their IPs. Definitely something which won't happen overnight.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm seeing the same sort of behavior from Verizon's looking glass server in New York:
traceroute to 94.140.14.14 (94.140.14.14), 30 hops max, 52 byte packets
1 0.ae13.GW14.NYC1.ALTER.NET (140.222.235.127) 0.936 ms 3.878 ms 3.068 ms
2 WS--Vodafone-Group-Services-Limited-Voda.customer.alter.net (204.148.1.254) 3.606 ms 1.264 ms 1.575 ms
3 ae0-xcr1.nyh.cw.net (195.2.25.70) 120.948 ms 122.097 ms 121.095 ms
MPLS Label=396305 CoS=0 TTL=1 S=1
4 et-10-3-0-xcr1.ptl.cw.net (195.2.24.242) 121.696 ms 121.571 ms 122.093 ms
MPLS Label=868061 CoS=0 TTL=1 S=1
5 ae29-xcr1.mlu.cw.net (195.2.24.229) 116.216 ms 116.002 ms 115.970 ms
MPLS Label=747209 CoS=0 TTL=1 S=1
6 ae23.0-xcr1.sof.cw.net (195.2.16.2) 102.332 ms 102.506 ms 102.293 ms
MPLS Label=119872 CoS=0 TTL=1 S=1
7 ae1-xcr1.ise.cw.net (195.2.18.209) 116.043 ms 110.482 ms 115.758 ms
8 cust-gw-ae3-17-xcr1.ise.cw.net (195.2.26.254) 121.584 ms 121.737 ms 116.560 ms
9 213.194.115.38 (213.194.115.38) 114.022 ms 119.523 ms 114.379 ms
10 * * *
11 185.137.215.90 (185.137.215.90) 118.845 ms 113.276 ms 118.553 ms
12 vl203.ist-mars-dist-2.cdn77.com (138.199.0.209) 113.397 ms vl201.ist-mars-dist-1.cdn77.com (138.199.0.207) 118.822 ms 118.674 ms
13 dns.adguard.com (94.140.14.14) 113.581 ms 113.220 ms 113.490 ms
Here's the BGP announcement from the same looking glass:
94.140.14.0/24 (2 entries, 1 announced)
*BGP Preference: 170/-101
Age: 1w3d 19:44:20 Metric: 0 Metric2: 504
Announcement bits (4): 0-KRT 3-RT 9-BGP_RT_Background 10-Resolve tree 4
AS path: 1273 15924 57152 60068 212772 I (Originator)
Communities: 0:201 701
Localpref: 100
BGP Preference: 170/-101
Age: 1w3d 19:44:20 Metric: 0 Metric2: 504
AS path: 1273 15924 57152 60068 212772 I (Originator)
Communities: 0:201 701
Localpref: 100
It appears AdGuard doesn't have transit from Verizon, so the BGP is preferring Vodafone and taking the route to Europe. I found AdGuard's East Coast POP which is hosted out of CDN77's network. On my ISP (Charter) I have to route through Comcast, which is one of CDN77's immediate transit providers. Although Charter has transit to CDN77 directly, my immediate AS heads to Comcast since Comcast is a more preferred peer. The preference is usually based on costs (such as, Comcast provides more bandwidth to CDN77 and for less money, therefore Comcast may be a better choice to direct user traffic through). In this case the cost decisions would be on CDN77, which would be upstream from AdGuard.
A change like this usually needs coordination from Verizon, as well as the intermediate networks to make sure the announcement for the New York Datacenter can get to Verizon on a more preferred path than Vodafone, It may also need to be something AdGuard needs to coordinate since they do have some control over BGP for their IPs. Definitely something which won't happen overnight.
