Frontier Communications → Re: Frontier Texas

Frontier 13 is companyspeak for 13 states that Frontier acquired from Verizon in 2010.

I'll plug that into my vocabulary database. Thanks.

Ahh wow, I actually thought it was just 3. Indiana, Oregon, and SC. I was never a wireline telco guy though, I'm with VES/Business aka the old MCI Worldcom. Outside of wireless, probably some of the only Verizon wireline employees left in TX.

Ok NOW I'm getting some latency, like 30ms to stuff that should be sub 10 ms.

Noticed this as well. Mainly the shared servers in the SoftLayer Dallas datacenter that I use. Was around 3 - 5 ms after the initial switch to Level3, and now about 40 ms. Although it looks like it may just be SoftLayer.

1 1 ms 1 ms 1 ms RT-N66U [192.168.1.1]
2 1 ms 2 ms 1 ms lo0-100.DLLSTX-VFTTP-316.verizon-gni.net [173.57.92.1]
3 4 ms 3 ms 3 ms 172.102.51.108
4 2 ms 2 ms 2 ms ae7---0.scr01.dlls.tx.frontiernet.net [74.40.3.17]
5 2 ms 2 ms 2 ms 74.40.4.14
6 * * 2 ms lag-102.ear3.Dallas1.Level3.net [4.15.44.125]
7 3 ms 3 ms 4 ms ae-2-70.edge5.Dallas3.Level3.net [4.69.145.78]
8 42 ms 43 ms 41 ms ae4-bbr01.eq01.dal03.networklayer.com [4.59.32.38]
9 42 ms 41 ms 43 ms ae6.dar02.dal05.networklayer.com [50.97.18.193]
10 42 ms 42 ms 42 ms po2.fcr03.sr03.dal05.networklayer.com [173.192.118.145]
11 41 ms 40 ms 42 ms web509.webfaction.com [184.172.15.237]

Yeah, looks like there's a reverse path latency issue. Look at it from the SoftLayer looking glass side and see where they're routing you.

1 webfaction.com (108.168.213.65) 0.331 ms 0.544 ms 0.542 ms
2 ae13.dar01.dal05.networklayer.com (173.192.118.142) 0.244 ms ae13.dar02.dal05.networklayer.com (173.192.118.144) 0.235 ms 4.326 ms
3 ae5.bbr01.eq01.dal03.networklayer.com (173.192.18.214) 0.948 ms ae21.bbr02.eq01.dal03.networklayer.com (50.97.18.194) 0.970 ms 0.956 ms
4 be-112-pe03.1950stemmons.tx.ibone.comcast.net (66.208.233.5) 1.910 ms 1.906 ms 1.642 ms
5 hu-0-4-0-7-cr02.dallas.tx.ibone.comcast.net (68.86.89.225) 3.441 ms hu-0-4-0-5-cr02.dallas.tx.ibone.comcast.net (68.86.86.149) 3.370 ms hu-0-4-0-3-cr02.dallas.tx.ibone.comcast.net (68.86.86.129) 3.361 ms
6 be-11524-cr02.losangeles.ca.ibone.comcast.net (68.86.87.173) 33.894 ms 35.860 ms 35.860 ms
7 be-10915-cr01.sunnyvale.ca.ibone.comcast.net (68.86.86.97) 41.361 ms 41.616 ms 41.907 ms
8 be-10925-cr01.9greatoaks.ca.ibone.comcast.net (68.86.87.158) 39.568 ms 39.533 ms 40.562 ms
9 hu-0-10-0-1-pe03.11greatoaks.ca.ibone.comcast.net (68.86.85.234) 41.215 ms 41.266 ms 41.495 ms
10 23.30.206.94 (23.30.206.94) 84.230 ms 84.467 ms 84.431 ms
11 B200.DLLSTX-LCR-21.verizon-gni.net (130.81.162.153) 78.941 ms 74.329 ms *
12 172.102.51.109 (172.102.51.109) 78.847 ms 172.102.51.79 (172.102.51.79) 78.766 ms 78.225 ms
13 173.74.xxx.xxx (173.74.xxx.xxx) 76.959 ms 80.688 ms 75.681 ms

CA Comcast
Would my web host have control over this (via SoftLayer), or is this a Frontier issue? Pinging around 80 ms tonight.

That's definitely a SoftLayer issue. They're routing reverse traffic over AS7922 (Comcast) when it should be...whatever Frontier is using. Will post back shortly with what that is.

SoftLayer should be able to fix the routing from their end. Probably best to get WebFaction to poke 'em for you though, since as an IBM subsidiary, well, yeah...
Just did some quick analysis from a server I've got in Dallas (vultr.com in case you're curious) and it looks like the easy fix would be to hard-code AS5650 (Frontier) to route via AS3356 (Level3). Just traced from here in Austin and from that server and both paths took Level3.

Right now, seems like the reverse traffic is taking the mother of all hairpins to CA and back, which makes zero sense.

Really appreciate your help and the info. I've sent in a support request to WebFaction. I included some of this info. and the (reverse) traceroute. I would think they have the clout to get SoftLayer to check into it. I'll let you know how it goes.