Topic 'Crazy stupid routing from San Angelo to Dallas' in forum 'Suddenlink' - dslreports.com

Re: Crazy stupid routing from San Angelo to Dallas

Tue, 01 Dec 2009 18:01:13 EDT

fuzion posted : Suddenlink decided that they were concerned with my satisfaction with recent interactions with their customer service reps... anyway, I took the survey and got an email address for this guy if anyone should ever need him ;)

Dave Gilles
Senior VP of Operations - West Region
westregionvp@suddenlink.com

Re: Crazy stupid routing from San Angelo to Dallas

Thu, 12 Nov 2009 22:46:52 EDT

e144539 posted : Wait they have FiOS in San Angelo now?
That's news to me! :p

Re: Crazy stupid routing from San Angelo to Dallas

Thu, 12 Nov 2009 00:04:26 EDT

fuzion posted : Actually, this appears to have been fixed... at least for my IP anyway. I haven't checked any others yet.

I contemplated switching to verizon, but they don't have fios on my street.

Re: Crazy stupid routing from San Angelo to Dallas

Wed, 11 Nov 2009 20:36:37 EDT

e144539 posted : This is why I left Suddenlink a couple of years ago.
I used them for four or five years (first as Cox). I had the problems in the "last mile" finally ironed out, and I was meeting my speed cap. They had to replace two bad amplifiers over two years. Why it needed to go through 20 amps to an optical node 2 miles to the north, when there is one three blocks to the east, and one of the lines coming off of it is right across the street, I still don't understand.

They were connecting with Level 3 in Dallas, but there was some packet loss and a lot of latency spikes. It made playing on my favorite game server nearly impossible.
That and now I only pay half the price and can live with the slower speed.
--

Never attribute to malice that which can be adequately explained by stupidity.

Re: Crazy stupid routing from San Angelo to Dallas

Tue, 10 Nov 2009 18:16:25 EDT

JeepMatt posted : Fuzion-
Awesome that they helped out!
--
"ONE team - ONE city - ONE dream!!"

Re: Crazy stupid routing from San Angelo to Dallas

Mon, 02 Nov 2009 15:27:42 EDT

gatorkram posted : I missed this thread somehow.

Great that you heard back from level3, and that it looks like your packets are taking a better path to your destination, or at least more logical, in a geographical standpoint.

Thumbs up all around.
--
Give me bandwidth or give me death!
»/testhistory/661871/4f240

Re: Crazy stupid routing from San Angelo to Dallas

Fri, 30 Oct 2009 18:28:26 EDT

iansltx posted : I'll bet Suddenlink resolved that issue, as they control the forward route. OTOH the reverse route is in the hands of ColoCrossing...might want to run a trace from them to you to see what the route taken is.

FWIW those are some decent pings on the first and second hops.

Re: Crazy stupid routing from San Angelo to Dallas

Fri, 30 Oct 2009 17:21:22 EDT

fuzion posted : Now I'm impressed.


1 <1 ms <1 ms <1 ms TEW-639GR [192.168.10.1]
2 7 ms 7 ms 7 ms 10.250.0.1
3 8 ms 7 ms 11 ms cdm-66-76-46-169.susp.suddenlink.net [66.76.46.169]
4 18 ms 15 ms 24 ms cdm-66-76-46-181.susp.suddenlink.net [66.76.46.181]
5 32 ms 32 ms 31 ms cdm-66-76-31-73.lfkn.suddenlink.net [66.76.31.73]
6 31 ms 31 ms 30 ms cdm-66-76-31-65.lfkn.suddenlink.net [66.76.31.65]
7 33 ms 30 ms 30 ms cdm-66-76-30-137.tylrtx.suddenlink.net [66.76.30.137]
8 31 ms 29 ms 29 ms cdm-66-76-30-6.tylrtx.suddenlink.net [66.76.30.6]
9 30 ms 31 ms 29 ms cdm-66-76-30-5.tylrtx.suddenlink.net [66.76.30.5]
10 67 ms 63 ms 65 ms te-7-4.car4.Dallas1.Level3.net [4.71.122.17]
11 220 ms 65 ms 110 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3]
12 69 ms 66 ms 66 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70]
13 66 ms 65 ms 65 ms unknown.dfw.colocrossing.com [72.249.94.148]

Suddenlink continues to ignore this issue, but Level3 technicians have corrected my outbound traffic so that my packets are no longer routed from Chicago and Denver. All of my inbound traffic is still routed slowly, but I believe that to be an issue with BGP tables since they all show Chicago as the optimal route for Texas traffic.

Now I await a response from Suddenlink...

Re: Crazy stupid routing from San Angelo to Dallas

Wed, 28 Oct 2009 19:15:55 EDT

iansltx posted : Wow, I'm impressed that you heard anything from L3 at all. Hopefully SL does some L3 routing through Dallas...where it would make a whole lot more sense (seeing as how L3 has to go to Denver before reaching Chicago from Dallas, unless SL has direct fiber between Dallas and Denver, which several providers could rent them).

Re: Crazy stupid routing from San Angelo to Dallas

Wed, 28 Oct 2009 19:00:59 EDT

fuzion posted : Got a response from level3 a week ago, but nothing has come of it yet. Here's the gist of what they had to say:

Suddenlink is a customer of ours. For whatever reason, they are advertising the route that encompasses your home IP address to Level 3 only in Chicago and not at other interconnect points with Level 3 that are potentially closer to you. If that is how they choose to route this traffic there is little we can do to change this. They are our customer and they are free to route their traffic in any fashion they choose. We have contacted them to offer additional assistance with improving this routing if they wish to do so. There's not much else we can do at the moment.

Way more help than I would have ever expected. Suddenlink is happily pissing off every customer in one of the largest markets.

Re: Crazy stupid routing from San Angelo to Dallas

Thu, 22 Oct 2009 23:19:33 EDT

iansltx posted : Your speeds suck, though looks like connectionq uality is fine, albeit with a higher than usual ping. Maybe try the Chicago server to see whether you get an A on PingTest (I'll bet you do). Jitter is in line with what I see on my Comcast connection.

Re: Crazy stupid routing from San Angelo to Dallas

Thu, 22 Oct 2009 22:20:28 EDT

fuzion posted : Thought it would be worth sharing my horrible speeds too:

I pay $60/mo for this crap.. I'm the stupid one it seems.

Re: Crazy stupid routing from San Angelo to Dallas

Thu, 22 Oct 2009 17:23:48 EDT

iansltx posted : It's Suddenlink's choice to haul traffic all the way up to Chicago to peer with Level3. Have no idea why they'd do that, but I saw that routing when I was on an SL connection last summer. Really crappy, especially since it'd make since for SL to just bring traffic into Dallas and drop it there.

Heck, they could buy a gigabit of transit from Hurricane Electric for $1500 per month or so (not much) and the performance would be better than going all the way out to Chicago and back!

Re: Crazy stupid routing from San Angelo to Dallas

Thu, 22 Oct 2009 16:53:31 EDT

fuzion posted : Very cool. Right now I am waiting for a response from the server host. If they decide they can't do anything either, I'll send one to level3 as well.

Re: Crazy stupid routing from San Angelo to Dallas

Thu, 22 Oct 2009 14:13:52 EDT

JeepMatt posted : Fuzion-
I'd also try contacting Level 3 with the same info -

lg.level3.net is a site that has a contact link on it
--
"ONE team - ONE city - ONE dream!!"

Re: Crazy stupid routing from San Angelo to Dallas

Wed, 21 Oct 2009 20:10:55 EDT

daroy990 posted : Not quite sure what you want them to do. They aren't going to lay a new fiber back haul line just for you.

Re: Crazy stupid routing from San Angelo to Dallas

Wed, 21 Oct 2009 19:28:46 EDT

fuzion posted : Just got this email from a 'supervisor'...

Hunt, Christopher
to me

4:26 PM (1 hour ago)

We follow the trace and due to these servers not being a part of Suddenlink we are unable to fix the lag time.

We do apologize for the inconvenience.

Thanks, Chris

Re: Crazy stupid routing from San Angelo to Dallas

Mon, 19 Oct 2009 19:41:13 EDT

JeepMatt posted : Your end site is definitely tied to L3. Here's my route on Verizon FIOS from Delaware.

Target Name: dallas.colocrossing.com
IP: 72.249.94.147

1 1 ms 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 5 ms 5 ms L100.PHLAPA-VFTTP-83.verizon-gni.net [98.114.x.x]
3 5 ms 4 ms 5 ms 7 ms G2-0-5-883.PHLAPA-LCR-08.verizon-gni.net [130.81.110.112]
4 4 ms 4 ms 5 ms 5 ms so-3-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.29.6]
5 99 ms 4 ms 8 ms 5 ms 0.so-6-0-0.XL2.PHL6.ALTER.NET [152.63.3.81]
6 15 ms 38 ms 13 ms 12 ms 0.so-5-2-0.XL4.IAD8.ALTER.NET [152.63.36.209]
7 N/A N/A N/A 12 ms 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.33.121]
8 12 ms N/A 11 ms 12 ms te-11-0-0.edge1.Washington4.level3.net [4.68.111.253]
9 N/A N/A 11 ms 17 ms vlan89.csw3.Washington1.Level3.net [4.68.17.190]
10 N/A N/A N/A 23 ms ae-81-81.ebr1.Washington1.Level3.net [4.69.134.137]
11 33 ms 35 ms 39 ms 28 ms ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
12 51 ms 49 ms 53 ms 62 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
13 49 ms 49 ms 51 ms 49 ms ae-41-90.car1.Dallas1.Level3.net [4.69.145.195]
14 50 ms 51 ms 51 ms 51 ms CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70]
15 51 ms 49 ms 51 ms 51 ms dallas.colocrossing.com [72.249.94.147]

Ping statistics for dallas.colocrossing.com
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 49ms, Maximum = 51ms, Average = 50ms
--
"ONE team - ONE city - ONE dream!!"

Re: Crazy stupid routing from San Angelo to Dallas

Mon, 19 Oct 2009 15:26:07 EDT

fuzion posted : I had Suddenlink in another city further West about 3 months ago and my ping and route to the same server were much lower... I know my packets stayed in state as well.

Re: Crazy stupid routing from San Angelo to Dallas

Mon, 19 Oct 2009 14:52:01 EDT

JeepMatt posted : Fuzion-
Most likely the only peering point SLink has with ColoCrossing is via Level 3.

Your local SLink connection peers with Level 3 in Chicago.

And the only L3 location that peers with Colo Crossing is in Dallas.

Hence, the routing you are seeing. I wouldn't expect too much on this one...but it could be worth your while to inquire.
--
"ONE team - ONE city - ONE dream!!"

Crazy stupid routing from San Angelo to Dallas

Mon, 19 Oct 2009 04:08:19 EDT

fuzion posted : A tracert to this dedicated box in Dallas gets routed from West/Central Texas to Chicago then to Denver then to Dallas.


  1    <1 ms    <1 ms    <1 ms  TEW-639GR [192.168.10.1]
  2   389 ms   304 ms     6 ms  10.250.0.1
  3     8 ms     7 ms     8 ms  cdm-66-76-46-169.susp.suddenlink.net [66.76.46.169]
  4    19 ms    18 ms    17 ms  cdm-66-76-46-181.susp.suddenlink.net [66.76.46.181]
  5    30 ms    28 ms    27 ms  cdm-66-76-31-73.lfkn.suddenlink.net [66.76.31.73]
  6    30 ms    29 ms    29 ms  cdm-66-76-30-125.tylrtx.suddenlink.net [66.76.30.125]
  7    33 ms    30 ms    29 ms  cdm-66-76-30-6.tylrtx.suddenlink.net [66.76.30.6]
  8   452 ms   435 ms   331 ms  66-76-232-17.tyrd.suddenlink.net [66.76.232.17]
  9    61 ms    59 ms    59 ms  66-76-232-1.tyrd.suddenlink.net [66.76.232.1]
 10    64 ms    59 ms    67 ms  xe-10-3-0.edge3.Chicago3.Level3.net [4.53.96.13]
 11    65 ms    71 ms    71 ms  ae-31-51.ebr1.Chicago1.Level3.net [4.68.101.30]
 12    61 ms    60 ms    61 ms  ae-6.ebr1.Chicago2.Level3.net [4.69.140.190]
 13    84 ms    89 ms    89 ms  ae-3.ebr2.Denver1.Level3.net [4.69.132.61]
 14    96 ms    89 ms    91 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
 15   406 ms   109 ms   105 ms  ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
 16   100 ms   100 ms    99 ms  ae-21-70.car1.Dallas1.Level3.net [4.69.145.67]
 17   318 ms   261 ms   379 ms  CWIE-LLC.car1.Dallas1.Level3.net [4.59.113.70]
 18    99 ms   116 ms    99 ms  dallas.colocrossing.com [72.249.94.147]

I called 'tech support' a few times, and they basically told me that they can only escalate for 'DNS' issues... any suggestions?