Domain Names/Static IP
Managing, controlling, and support for Custom Domain Names
Male IT Specialist Holds Laptop and Discusses Work with Female Server Technician. They're Standing in Data Center, Rack Server Cabinet is Open.
Highlighted
Visitor

Comcast routing my busniess static IP a bad path compair resident DHCP IPs path.

I try so many times to talk to tech support on this, they just don't understand how BGP and peering works....

 

I am trying to access a colo server at Serverna.net and I notice my business static IP are getting a constant ~10% packet loss up to 100ms latency. If I use my neighbor's Comcast that is a resident DHCP 0% packet loss with at a steady 20ms latency to the same colo server. Seems kinda on unfair to have Comcast send its business customer to a worse path then a lower paying customer.

 

from the server to my Comcast business IP:

 

[root@server ~]# ping 173.164.225.XX -A -c 100 -q
PING 173.164.225.XX (173.164.225.XX) 56(84) bytes of data.

--- 173.164.225.XX ping statistics ---
100 packets transmitted, 92 received, 8% packet loss, time 5865ms
rtt min/avg/max/mdev = 43.549/57.743/87.025/9.627 ms, pipe 2, ipg/ewma 59.249/62.106 ms
[root@server ~]#

 

and here is from the server to a comcast DHCP IP:

 

[root@server ~]# ping 73.170.59.XX -A -c 100 -q
PING 73.170.59.XX (73.170.59.XX) 56(84) bytes of data.

--- 73.170.59.XX ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 3592ms
rtt min/avg/max/mdev = 19.685/38.114/71.421/10.432 ms, pipe 2, ipg/ewma 36.289/41.049 ms
[root@server ~]#

 

 

Here is the path that Comcast is advertising my static IP to:

 

[root@server ~]# traceroute 173.164.225.XX
traceroute to 173.164.225.XX (173.164.225.XX), 30 hops max, 60 byte packets
1 gateway (172.86.146.1) 0.422 ms 0.515 ms 0.565 ms
2 p21.20g.csr1.Lax1.Servernap.net (66.252.6.34) 0.543 ms 0.621 ms 0.662 ms
3 ae0.er1.Lax1.Servernap.net (66.252.6.33) 0.179 ms 0.201 ms 0.185 ms
4 te0-0-0-34.ccr23.lax05.atlas.cogentco.com (38.104.84.133) 1.959 ms 2.373 ms 2.480 ms
5 be2180.ccr21.lax01.atlas.cogentco.com (154.54.41.57) 0.935 ms 0.872 ms be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81) 0.905 ms
6 be2161.ccr22.sjc01.atlas.cogentco.com (154.54.27.170) 13.033 ms be2160.ccr21.sjc01.atlas.cogentco.com (154.54.27.162) 12.969 ms be2161.ccr22.sjc01.atlas.cogentco.com (154.54.27.170) 13.445 ms
7 be2165.ccr22.sfo01.atlas.cogentco.com (154.54.28.65) 14.442 ms 14.356 ms be2164.ccr21.sfo01.atlas.cogentco.com (154.54.28.33) 14.437 ms
8 be2077.ccr22.sea01.atlas.cogentco.com (154.54.0.242) 33.279 ms 33.271 ms 33.273 ms
9 be2084.ccr21.sea02.atlas.cogentco.com (154.54.0.254) 33.508 ms 33.578 ms be2083.ccr21.sea02.atlas.cogentco.com (154.54.0.250) 33.384 ms
10 be-205-pe04.seattle.wa.ibone.comcast.net (66.208.228.109) 34.403 ms 34.338 ms 34.378 ms
11 hu-1-2-0-2-cr01.seattle.wa.ibone.comcast.net (68.86.86.137) 34.827 ms hu-1-2-0-3-cr01.seattle.wa.ibone.comcast.net (68.86.85.37) 34.744 ms hu-1-2-0-4-cr01.seattle.wa.ibone.comcast.net (68.86.82.225) 34.726 ms
12 be-10825-cr01.9greatoaks.ca.ibone.comcast.net (68.86.85.198) 35.094 ms 35.079 ms 35.038 ms
13 be-7922-ar01.hayward.ca.sfba.comcast.net (68.86.94.154) 36.034 ms 35.886 ms 34.890 ms
14 hu-0-7-0-1-sur04.sanjose.ca.sfba.comcast.net (68.87.192.238) 36.588 ms hu-0-4-0-2-sur04.sanjose.ca.sfba.comcast.net (68.87.194.126) 35.948 ms hu-0-4-0-0-sur04.sanjose.ca.sfba.comcast.net (68.87.192.226) 36.109 ms
15 te-7-0-acr10.sanjose.ca.sfba.comcast.net (162.151.30.26) 34.668 ms 34.771 ms 34.686 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 *^C
[root@server ~]#

 

and here is a traceroute to comcast DHCP IP:

[root@server ~]# traceroute 73.170.59.XX
traceroute to 73.170.59.XX (73.170.59.XX), 30 hops max, 60 byte packets
1 gateway (172.86.146.1) 0.637 ms 0.668 ms 0.679 ms
2 p21.20g.csr1.Lax1.Servernap.net (66.252.6.34) 0.406 ms 0.435 ms 0.500 ms
3 ae0.er1.Lax1.Servernap.net (66.252.6.33) 0.233 ms 0.212 ms 6.905 ms
4 PCCW.er1.Lax1.Servernap.net (66.252.6.142) 0.844 ms 0.925 ms 1.004 ms
5 63-218-73-174.static.pccwglobal.net (63.218.73.174) 1.234 ms 1.368 ms 1.443 ms
6 hu-0-4-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.85.97) 2.898 ms hu-0-4-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.85.93) 1.222 ms hu-0-4-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.85.29) 3.290 ms
7 be-10915-cr01.sunnyvale.ca.ibone.comcast.net (68.86.86.97) 159.730 ms 159.884 ms 160.123 ms
8 be-7922-ar01.santaclara.ca.sfba.comcast.net (68.86.90.94) 11.947 ms 11.971 ms 12.016 ms
9 hu-0-4-0-0-sur03.sanjose.ca.sfba.comcast.net (68.87.192.162) 11.872 ms hu-0-4-0-2-sur03.sanjose.ca.sfba.comcast.net (68.87.194.122) 11.913 ms 11.890 ms
10 te-6-0-acr10.sanjose.ca.sfba.comcast.net (162.151.30.18) 12.030 ms 12.083 ms 12.396 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 *^C
[root@server ~]#

 

It would be nice if comcast would not be doing this to me.

0 Kudos
Reply
2 REPLIES 2
Highlighted
Visitor

Re: Comcast routing my busniess static IP a bad path compair resident DHCP IPs path.

can any body fix this routing issue? been going on for a while now.

0 Kudos
Reply
Highlighted
Visitor

Re: Comcast routing my busniess static IP a bad path compair resident DHCP IPs path.

route change was just done, latency and packetloss went away and both networks are now taking the same path.

0 Kudos
Reply