ATT <-> Broadwing (Level3) Congestion

Is anyone else seeing significant congestion between ATT and Broadwing in Dallas/Fort Worth?


Is anyone else seeing significant congestion between ATT and Broadwing in Dallas/Fort Worth?


I have no idea if the following is related: (and frankly, I don't care, for anyone that wants to flame me on it) :wink:

I was seeing it between Qwest and Level 3 since about November(!!!), on and off. And getting worse over the months. You know it's bad when residential customers send traceroutes and ping summaries saying "Um, 6 hops out, Qwest is broken in Dallas." When I would call Qwest on it, I would get one clueless in-duh-vidual after another. Eventually, I did get a cluefull chap who summed it up with "Yeah, that's a big political finger pointing debacle." He wouldn't comment further, and I don't blame him.

(Sidebar... it's funny that as a PAYING CUSTOMER I have to talk to the front line support doofs... if I were a NON-PAYING CUSTOMER (peer) with them, I'd get to talk to some cluefull NOC person that knows what the phrase "IP transit" means.)

A week ago, admin downed my BGP session with Qwest. Life was instantly 100% better.

Maybe it was Qwest's fault. Or Maybe it Level3's fault the whole time. I don't care who's fault it is.... L3 or Qwest, or the man on the moon.....As far as I'm concerned, when two large NSPs can't get a peering arrangement to not have packet loss, they both suck equally, because they're both being equally STUPID in not solving the problem. It's not like they can't afford to upgrade something. If it's really that big of a deal, down the peering session! Transit the traffic on your own backbones to a peering session somewhere else! Idiots! Argh!!

In this case, by firing Qwest, I had the ability to punish stupid. And it felt good. Because over the months, my customers have done the same to me by leaving due to crappy performance.

This week, I'm no longer a Qwest transit customer. And I'm sleeping better at night, and my family life is even better. Life's good!

Just my two cents.

Hash: SHA1


Brandon Galbraith wrote:

Is anyone else seeing significant congestion between ATT and Broadwing in
Dallas/Fort Worth?


- --------------------------
Not that I can tell. Not sure what others are seeing.

Level 3 (Dallas, TX) Ping to (timewarner) looks ok.

icmp_seq=0 time=44 ms
icmp_seq=1 time=40 ms
icmp_seq=2 time=40 ms
icmp_seq=3 time=44 ms
icmp_seq=4 time=40 ms
icmp_seq=5 time=40 ms
icmp_seq=6 time=40 ms
icmp_seq=7 time=40 ms
icmp_seq=8 time=40 ms
icmp_seq=9 time=44 ms

- ---- statistics ----
10 packets transmitted, 10 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 40/41.2/40/44/1.296/1.833 ms

Level 3 (Dallas, TX) Traceroute to (timewarner) look ok.

  1 ( 8 msec * ( 4 msec
  2 ( 32 msec 32 msec ( 8 msec
  3 ( 32 msec 32 msec ( 68 msec
  4 ( 32 msec ( 32 msec ( 100 msec
  5 ( 32 msec ( 32 msec ( [AS20001
  6 ( [AS20001
{ROADRUNNER-WEST}] 32 msec 36 msec ( [AS20001
  7 ( [AS20001
{ROADRUNNER-WEST}] 32 msec 36 msec ( [AS20001
  8 * * 40 msec
  9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * * timeout !

Do you have an ip address to test?


Thanks to all who responded privately as well as publicly. It looks like the problem has been resolved at the peering/transit point in question.