US Telco Support > AT&T > AT&T Southeast > Why the different route?

Why the different route?

My trace route has done the same thing as yours. It also knocked my speeds down a little bit. I never have been able to figure out why my gateway is in Jacksonville, Fla. to begin with. Coupled with the news about the BS techs not being able to help here or in the newsgroups and this mess, I'm seriously thinking about a local ISP that now has DSL.

NeoTrace Trace Version 3.25 Results
Target: www.broadbandreports.com
Date: 12/7/2002 (Saturday), 4:07:45 AM
Nodes: 15

Node Data
Node Net Reg IP Address Location Node Name
1 - - 192.168.1.100 31.701N, 89.144W 9gwxc01
2 1 1 Jacksonville adsl-156jan.bellsouth.net
3 2 1 Jacksonville adsl-811.jan.bellsouth.net
4 3 - 205.152.137.248 Unknown
5 2 - 65.83.237.86 Unknown
6 2 - 65.83.236.32 Unknown
7 4 2 65.208.10.245 New Orleans 500.so-1-0-0.gw5.nol1.alter.net
8 5 2 152.63.102.98 New Orleans 0.so-3-0-0.cl1.nol1.alter.net
9 5 2 152.63.0.193 Dallas 0.so-0-0-0.tl1.dfw9.alter.net
10 5 2 152.63.1.118 New York 0.so-2-2-0.tl1.nyc9.alter.net
11 5 - 152.63.27.29 Unknown
12 5 2 152.63.19.85 New York 0.so-0-0-0.xr1.nyc1.alter.net
13 5 2 152.63.25.73 New York 507.atm7-0.gw7.nyc1.alter.net
14 6 2 157.130.9.142 Unknown nac-nyc-gw1.customer.alter.net
15 7 3 209.123.109.175 Unknown www.broadbandreports.com

Packet Data
Node High Low Avg Tot Lost
1 0 0 0 1 0
2 55 18 36 2 0
3 17 17 17 1 0
4 17 17 17 1 0
5 32 32 32 1 0
6 21 21 21 1 0
7 20 20 20 1 0
8 20 20 20 1 0
9 35 35 35 1 0
10 71 71 71 1 0
11 69 69 69 1 0
12 69 69 69 1 0
13 71 71 71 1 0
14 74 74 74 1 0
15 72 72 72 1 0

Network Data
Network id#: 1

OrgName: BellSouth.net Inc.
OrgID: BELL

Network id#: 2

OrgName: BellSouth.net Inc.
OrgID: BELL

Network id#: 3

OrgName: BellSouth.net Inc.
OrgID: BELL

Network id#: 4

OrgName: UUNET Technologies, Inc.
OrgID: UU

Network id#: 5

OrgName: UUNET Technologies, Inc.
OrgID: UU

Network id#: 6

OrgName: UUNET Technologies, Inc.
OrgID: UU

Network id#: 7

OrgName: Net Access Corporation
OrgID: NAC

Registrant Data
Registrant id#: 1
Registrant:
Bell South Intellectual Property Corporation (BELLSOUTH-DOM)
824 Market Street Suite 510
null
US

Registrant id#: 2
Registrant:
UUNET Technologies, Inc. (ALTER-DOM)
3060 Williams Drive
Falls Church
VA,22031
US

Registrant id#: 3
See Registrant Pane for registrant contact information.

_____
NeoTrace Copyright ©1997-2001 NeoWorx Inc

reply to jazzman916
The answer to your questions are they use routing when one loop is busy you are routed to a less busy server {gateway} that way you are using the fastest route possible. I hope this answers your question and helps you understand what you are seeing.
crirvine

reply to jazzman916
Mine has changed too. All our traffic used to go all the way up to Indiana, then to Chicago and then off to the net. Looks were going threw Tennessee, to Atlanta then off to the rest of the net now. UUNET has defiantly changed routes.
--
"Raymond Shaw is the kindest, bravest, warmest, most wonderful human being I've ever known in my life." - Bennett Marco

reply to jazzman916
My tracert wont work

tracert www.dslreports.com

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms SpeedTouch.lan [10.0.0.138]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.

said by joako:

---

My tracert wont work

tracert www.dslreports.com

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms SpeedTouch.lan [10.0.0.138]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.

---

reply to jazzman916
i have bsfa and a frac t-1. the frac started getting some serious dropped packets the other day. i talked to the isp it goes through, not bs, and they said bell had changed alot of their routing (bell's) and didn't inform them. this caused them to have major problems with restricted usable bandwidth due to packets timing out. looks like bell did their usual and just changed things and said we will fix any problems later when they pop up and folks complain. i may not be that old, but i was taught "if it ain't broke, don't fix it!" seems someone needs to teach this to bell.

reply to crirvine
Not entirely true

The way I understand it, UUNet changed the routing on purpose.

It's happened before in the past.

There was a post by Andy Houtz a year, or two, or three years ago where this had happened before. I can't find the post or thread, but I know it's somewhere in this site's history.

Thanks to Jassman916 for referring me to this thread.

Seems Alabama is affected as well:
»ATTN: Birmingham, AL users, please read

My traceroute is:
1 1 ms 1 ms 1 ms host1-null.null.bellsouth.net [192.168.1.1]
2 1 ms 1 ms 1 ms host-null.bellsouth.net [10.0.0.138]
3 18 ms 16 ms 16 ms adsl-17-184-1.bhm.bellsouth.net [68.17.184.1]
4 19 ms 17 ms 16 ms adsl-21-226-33.bhm.bellsouth.net [66.21.226.33]
5 17 ms 16 ms 15 ms 207.203.159.185
6 26 ms 25 ms 24 ms 65.83.237.42
7 26 ms 25 ms 24 ms 65.83.236.36
8 25 ms 26 ms 25 ms 500.so-1-0-0.GW5.NOL1.ALTER.NET [65.208.10.245]
9 26 ms 26 ms 26 ms 0.so-2-0-0.CL2.NOL1.ALTER.NET [152.63.102.94]
10 39 ms 39 ms 40 ms 0.so-0-0-0.TL2.DFW9.ALTER.NET [152.63.2.181]
11 73 ms 74 ms 75 ms 0.so-6-0-0.TL2.NYC9.ALTER.NET [152.63.13.10]
12 77 ms 75 ms 74 ms 0.so-3-0-0.XL2.NYC1.ALTER.NET [152.63.29.113]
13 73 ms 74 ms 73 ms 0.so-0-0-0.XR2.NYC1.ALTER.NET [152.63.19.97]
14 75 ms 74 ms 77 ms 508.ATM7-0.GW7.NYC1.ALTER.NET [152.63.25.85]
15 77 ms 77 ms 76 ms nac-nyc-gw1.customer.alter.net [157.130.9.142]
16 79 ms 78 ms 78 ms www.dslreports.com [209.123.109.175]

I used to go from Birmingham to Atlanta to New York, but not anymore.
--
"When you set yourself on fire and aim for the sky, you hope to leave behind some sparks of heat and light ... Like a vapor trail." - Neil Peart 2002

reply to jazzman916
This is not at all good. My speeds are down. My latency is up 70%. Not good at all.

With all of the changes I feel myself quickly slipping through their fingers. If you look back through the thread for the past one and half years you'll see I'm not one of the customers who constantly complains. Until the past couple of days I've only mentioned the news server once quite some time ago and only because BS asked us for a list of problems with their service. So when you see me complaining, it's getting bad.

[text was edited by author 2002-12-08 04:50:55]

Looks like Atlanta is/was overloaded:

said by WorldCom NOC: »www1.worldcom.com/us/tools/maintmsg/

---

During the normal operations window on Tuesday, December 10th, 2002, WorldCom will be performing maintenance in the following cities:

Atlanta, GA(ATL2, ATL7); Boston, MA(BOS10); Baton Rouge, LA(BTRG); Chicago, IL(CHI1, CHI6); Columbus, OH(CMBR); Washington, DC(DCA8); Denver, CO(DEN1, DEN4); Dallas, TX(DFW9, DLLS); Newark, NJ(EWR1, EWR3); Houston, TX(HOU7); Los Angeles, CA(LAX7); Miami, FL(MIA4); Memphis, TN(MMPH=MEM1); New York, NY(NYC4); Raleigh, NC(RLGH); San Antonio, TX(SAT1); Seattle, WA(SEA9, SEA10); San Francisco, CA(SFO4); San Jose, CA(SJC5); Salt Lake City, UT(SLT1); Shreveport, LA(SREV); Saint Louis, MO(STL3); Vienna, VA(TCO2, TCO3); Troy, MI(TROY); Vicksburg, MS(Vicksburg-da.ms)

These maintenances will result in additional capacity in order to meet expected customer demands. The maintenances will start at 3:00 a.m. local time at the affected sites.

---

I hope the ultimate goal was to temporarily re-route everyone until the upgrades were complete.

said by FROSTY:

---

I hope the ultimate goal was to temporarily re-route everyone until the upgrades were complete.

---

reply to jazzman916
Yes, much to my dismay, I've discovered this, also.

reply to jazzman916
Man, you guys tanking on that Texas to NYC hop, it's not great for the Atlanta to NYC hop, but it ain't that bad.
Maybe this is part of WorldCom/UUNET's restructuring, they used to be the best internet backbone, but it looks like they are loosing it.

reply to jazzman916
I just got off the phone with the helpdesk.

The person I spoke to was willing to help, but didn't know the correct course of action since it was a UUNet issue. When I mentioned I had heard that the UUNet Compliance Team is the group that's supposedly responsible for the Internet routing, he told me he was going to contact a few people and call me back...

BTW, I'm at home instead of work today. I hurt my back and they don't want me at work on pain killers.
--
"When you set yourself on fire and aim for the sky, you hope to leave behind some sparks of heat and light ... Like a vapor trail." - Neil Peart 2002

I called the help desk yesterday and he didn't know anything about it either. Maybe if everybody whose routes have changed would start calling and complaining, somebody might find out the reason for the change.

Mine changed for the better went from 60's to 50's to dslreports. I hope they don't change me back or overload my current route.
--
"Raymond Shaw is the kindest, bravest, warmest, most wonderful human being I've ever known in my life." - Bennett Marco

reply to jazzman916

Throwmaster,
You lucky dog. Must be because you're close to Atlanta and not as much traffic comes from the Auburn area. Plus you're on ATL5, I think we were routed though ATL7 until the change.

The tech I talked to yesterday basically confirmed I had no dropped packets, and that everything was operating in the norm. He understood my complaint about the routing, but said there was nothing he could do about it since the routing was controlled by WorldCom / UUnet.

He did tell me that in the years he's been working the helpdesk, I was the first person he had spoken to that had such a concern with routing. Because of this, he took the time to talk to several groups on my behalf. Which I thanked him for. Nonetheless, he said there was nothing he could do about it.

While some may like the routing change, I don't... The change has improved west coast communication, but hindered east coast.
--
"When you set yourself on fire and aim for the sky, you hope to leave behind some sparks of heat and light ... Like a vapor trail." - Neil Peart 2002

I agree with you completely Frosty. I am in the exact same boat you are, but at least we have the option not to use Charter.