[172350] in North American Network Operators' Group
Re: Can anyone check this routing against Charter in WI?
daemon@ATHENA.MIT.EDU (Michael Clark)
Sun Jun 15 20:21:05 2014
X-Original-To: nanog@nanog.org
From: Michael Clark <mikeal.clark@gmail.com>
In-Reply-To: <CAJxVgBKZCYLk+w3L8hCQ6dSd3demyV0Xkte-+vuhYbpq-rVcRw@mail.gmail.com>
Date: Sun, 15 Jun 2014 19:20:54 -0500
To: Rusty Dekema <rdekema@gmail.com>
Cc: "=?utf-8?Q? NANOG_=E2=80=8E\[nanog=40nanog.org\]=E2=80=8E ?="
<nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Well my routing isn't nearly that bad. I haven't been able to get confirmat=
ion but support said they are probably just routing around a problem and the=
y can't get any direct feedback form network engineers.=20
I should get an update tomorrow hopefully. I'm also seeing some bandwidth i=
ssues on charters internal network. Something must be going on.
Best to have up and go get some Bells :)
Sent from my iPhone
> On Jun 15, 2014, at 7:10 PM, Rusty Dekema <rdekema@gmail.com> wrote:
>=20
> Are you still seeing odd routing with Charter in Wisconsin? Charter's rout=
ing in Michigan seems to be going pretty crazy at the moment as well.=20
>=20
> The following traceroute is from a Charter residential line* in Kalamazoo M=
I to a Comcast business (DOCSIS) line in Ypsilanti MI, by way of several unk=
nown hops, some of which are in RFC 1918 space, Sprintlink possibly in Fort W=
orth TX, another unknown hop, then Comcast Dallas TX, Comcast Marietta GA, C=
omcast Ashburn VA, then finally Comcast MI. Needless to say, this is not the=
normal route:
>=20
> http://pastebin.com/9CKmea6M
>=20
> Tracing the same route but in the other direction also yields odd results.=
The route proceeds normally to a Comcast ibone router in 350 E. Cermak (Chi=
cago IL), but the very next hop after that router is the public IP of the Ch=
arter service in Kalamazoo MI as follows:
>=20
> http://pastebin.com/VCCgnUsn
>=20
> For what it's worth, if anyone could explain to me what might cause that b=
ehavior (between hops 8 and 9), I would really appreciate the knowledge.
>=20
> The routing between that same Charter residential service and a Merit/Mich=
net endpoint in southeast Michigan is also odd, taking a detour through Virg=
inia [xe-8-3-0.1018.asbn0.tr-cps.internet2.edu (198.71.47.25)], which it doe=
s not normally do. The routing in that case does appear to be the same regar=
dless of which side you initiate the traceroute from.
>=20
> Cheers,
> Rusty Dekema
>=20
>=20
> * The Charter residential line's IP address is currently reverse resolving=
to a Charter DHCP pool in Bay City, MI, which is over 100 miles from Kalama=
zoo. This is also unusual. The Charter service in question is now and has al=
ways been located in Kalamazoo MI. =20
>=20
>=20
>=20
>=20
>> On Sat, Jun 14, 2014 at 1:01 PM, Mikeal Clark <mikeal.clark@gmail.com> wr=
ote:
>> Hoping someone auditing the list can provide some insight or a back
>> channel support option.
>>=20
>> I started having some good latency spikes last night, which have
>> continued this morning, so I finally took a look at things and I am
>> seeing a lot more routing than I expected. Support is telling me this
>> is normal but I don't remember this many replies on traceroute. My
>> speeds are about 1/5 the normal as well this morning and seeing some
>> dropped packets even using a test sight inside Charter's network.
>> This is just business cable so my support options are pretty limited.
>>=20
>> 4 10 ms 14 ms 13 ms
>> dtr01shbywi-tge-0-3-0-23.shby.wi.charter.com [96.34.24.178]
>> 5 18 ms 11 ms 17 ms dtr01wbndwi-bue-2.wbnd.wi.charter.com
>> [96.34.30.17]
>> 6 12 ms 11 ms 11 ms dtr02wbndwi-bue-1.wbnd.wi.charter.com
>> [96.34.24.56]
>> 7 17 ms 11 ms 11 ms dtr02fdulwi-bue-3.fdul.wi.charter.com
>> [96.34.30.19]
>> 8 13 ms 18 ms 18 ms dtr01fdulwi-bue-1.fdul.wi.charter.com
>> [96.34.19.144]
>> 9 19 ms 14 ms 15 ms crr03fdulwi-bue-2.fdul.wi.charter.com
>> [96.34.20.8]
>> 10 30 ms 22 ms 35 ms crr02euclwi-bue-6.eucl.wi.charter.com
>> [96.34.22.240]
>> 11 23 ms 22 ms 43 ms bbr02euclwi-bue-4.eucl.wi.charter.com
>> [96.34.2.6]
>> 12 22 ms 34 ms 19 ms bbr01euclwi-bue-5.eucl.wi.charter.com
>> [96.34.0.6]
>> 13 34 ms 30 ms 38 ms
>> bbr01stcdmn-tge-0-0-0-3.stcd.mn.charter.com [96.34.0.115]
>> 14 42 ms 43 ms 52 ms 65.46.47.77
>> 15 78 ms 78 ms 92 ms ae1d0.mcr2.minneapolis-mn.us.xo.net
>> [216.156.1.86]
>> 16 93 ms 82 ms 82 ms vb1711.rar3.denver-co.us.xo.net [216.156.=
0.173]
>> 17 81 ms 95 ms 82 ms te-3-0-0.rar3.sanjose-ca.us.xo.net
>> [207.88.12.58]
>> 18 83 ms 82 ms 98 ms 207.88.14.226.ptr.us.xo.net [207.88.14.22=
6]
>> 19 81 ms 78 ms 78 ms 216.156.84.6.ptr.us.xo.net [216.156.84.6]=
>> 20 77 ms 78 ms 88 ms
>> xe-2-2-0-955.jnrt-edge02.prod1.netflix.com [69.53.225.30]
>> 21 86 ms 78 ms 78 ms te1-8.csrt-agg02.prod1.netflix.com
>> [69.53.225.10]
>> 22 79 ms 78 ms 82 ms www.trynetflix.com [69.53.236.17]
>>=20
>> 4 12 ms 11 ms 8 ms
>> dtr01shbywi-tge-0-3-0-23.shby.wi.charter.com [96.34.24.178]
>> 5 17 ms 10 ms 12 ms dtr01wbndwi-bue-2.wbnd.wi.charter.com
>> [96.34.30.17]
>> 6 11 ms 9 ms 15 ms dtr02wbndwi-bue-1.wbnd.wi.charter.com
>> [96.34.24.56]
>> 7 15 ms 18 ms 18 ms dtr02fdulwi-bue-3.fdul.wi.charter.com
>> [96.34.30.19]
>> 8 16 ms 14 ms 11 ms dtr01fdulwi-bue-1.fdul.wi.charter.com
>> [96.34.19.144]
>> 9 20 ms 14 ms 15 ms crr03fdulwi-bue-2.fdul.wi.charter.com
>> [96.34.20.8]
>> 10 22 ms 22 ms 18 ms crr02euclwi-bue-6.eucl.wi.charter.com
>> [96.34.22.240]
>> 11 18 ms 22 ms 22 ms bbr02euclwi-bue-4.eucl.wi.charter.com
>> [96.34.2.6]
>> 12 35 ms 30 ms 31 ms bbr01chcgil-bue-1.chcg.il.charter.com
>> [96.34.0.9]
>> 13 27 ms 27 ms 27 ms prr01chcgil-bue-2.chcg.il.charter.com
>> [96.34.3.9]
>> 14 27 ms 27 ms 27 ms
>> 96-34-152-30.static.unas.mo.charter.com [96.34.152.30]
>> 15 29 ms 32 ms 27 ms 209.85.244.1
>> 16 27 ms 27 ms 28 ms 209.85.254.238
>> 17 54 ms 40 ms 40 ms 209.85.248.214
>> 18 38 ms 40 ms 38 ms 216.239.43.217
>> 19 * * * Request timed out.
>> 20 44 ms 40 ms 40 ms google-public-dns-a.google.com [8.8.8.8]
>=20
