www.broadbandreports.com
  
Search:  

 
 
   AllHot TopicsCable SupportTelco SupportHardware etcSecurityClubsGallery»»






how-to block ads


 
Forums » US Telco Support » AT&T » AT&T Southeast » [Xtreme] 60+ High Ping to NFO Game Server starting around 4/1/8
 
Search Topic:
  Social:
topic feed
 
Posting
toggle:
flat / full
normal / watch
Post a:
Post a:
Why did AT&T send me a Motorola 2210 modem? »
« Dry loop DSL with existing POTS and shared DSL  
AuthorAll Replies


SDSuperman

@bellsouth.net

 [Xtreme] 60+ High Ping to NFO Game Server starting around 4/1/8

Can someone point me in the direction of help?

Starting around 4/1/8 I started getting a 60+ ping to an Atlanta NFO UT2004 server. I've played on this server for many months and usually have a ping from 18-36 can provide nice screen shots of this as proof. I have spoken with my ISP at&t/bellsouth and they have told me basically oh well your connected to the internet. I have also spoken to a Level3 communication technician and she told me that my ISP would have to initiate a trouble ticket with them because they do not deal with residential customers. However my ISP at&t tells me that they can not do this because once it leaves their network they are not responsible.

I believe the problem starts at hop #12 were it jumps off the at&t/bellsouth network with a nice 24 and goes to Level3 up to a 66.

Hop #13 will flip flop between 4.68.103.3 & 4.68.103.35 - ping here will jump from min.60 to max. 267 with avg. 62-88
ae-12-51.car2.Atlanta1.Level3.net [4.68.103.3]
ae-22-52.car2.Atlanta1.Level3.net [4.68.103.35]

Target Name: c-64-94-238-35.internap-atlanta.nuclearfallout.net
IP: 64.94.238.35
Date/Time: 4/23/2008 11:02:28 PM

1 0 ms 0 ms 0 ms [192.168.2.1]
2 0 ms 0 ms 0 ms launchmodem [192.168.1.254]
3 17 ms 17 ms 16 ms [68.208.232.7]
4 17 ms 17 ms 17 ms [65.14.199.101]
5 25 ms 26 ms 24 ms ber00hsv-pos-7-0-0.bellsouth.net [205.152.22.64]
6 25 ms 24 ms 25 ms ixc01bhm-pos-5-0-0.bellsouth.net [65.83.239.116]
7 24 ms 25 ms 24 ms ixc00bhm-ge-0-0-0.bellsouth.net [207.203.159.64]
8 24 ms 24 ms 24 ms [65.83.237.144]
9 24 ms 25 ms 23 ms axr00aep-ge-5-0-0.bellsouth.net [65.83.238.34]
10 25 ms 26 ms 25 ms axr01msy-0-3-1.bellsouth.net [65.83.236.31]
11 24 ms 24 ms 24 ms AXR00AEP-0-1-0.bellsouth.net [65.83.236.50]
12 66 ms 68 ms 66 ms so-7-0-0.edge1.Atlanta2.Level3.net [4.71.192.21]
13 -32764 ms 161 ms 275 ms ae-12-51.car2.Atlanta1.Level3.net [4.68.103.3]
14 62 ms 62 ms 63 ms internap.level3.net [209.246.169.150]
15 55 ms 55 ms 55 ms border6.pc2-bbnet2.acs.pnap.net [64.94.0.75]
16 66 ms 67 ms 66 ms c-64-94-238-35.internap-atlanta.nuclearfallout.net [64.94.238.35]

Any help is greatly appreciated in getting my ping back to were I was spoiled at 24.

FastAttack
Premium
join:2000-07-28
Fort Lauderdale, FL
clubs:
·AT&T Southeast
·T-Mobile US

Re: [Xtreme] 60+ High Ping to NFO Game Server starting around 4/

Tracing route to c-64-94-238-35.internap-atlanta.nuclearfallout.net [64.94.238.3
5]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 8 ms 9 ms 8 ms 65.14.252.3
3 9 ms 10 ms 9 ms 65.14.254.173
4 9 ms 9 ms 10 ms 65.83.237.130
5 10 ms 10 ms 11 ms pxr00mia-1-0-0.bellsouth.net [65.83.236.20]
6 18 ms 18 ms 18 ms 65.83.237.246
7 18 ms 19 ms 18 ms ge-1-2-0.bbr2.Miami1.Level3.net [4.68.112.45]
8 20 ms 20 ms 20 ms as-0-0.bbr2.Atlanta1.Level3.net [64.159.3.250]
9 267 ms 236 ms 236 ms ae-22-52.car2.Atlanta1.Level3.net [4.68.103.35]

10 22 ms 23 ms 24 ms internap.level3.net [209.246.169.150]
11 22 ms 24 ms 22 ms border6.pc1-bbnet1.acs.pnap.net [64.94.0.11]
12 25 ms 24 ms 24 ms c-64-94-238-35.internap-atlanta.nuclearfallout.n
et [64.94.238.35]
-----------------

level 3 is doing fine even though car2 seems to be high.. it is most likely its priority settings for ping request to that particular router is set to very low...

as a gamer i understand your frustrations but there is really nothing you can do with the peering between level 3 and bellsouth..

but there is something you can do:

1 seems like you are interleave mode adding some latency to your connection.. as you can see in my trace my first hop is 8ms.. which is normal on fastpath connections..

also i noticed some extra hops in your connection, if you are on interleaved + extra hops = higher ping..

maybe its a good idea to tell us what speed package you have and then post your connection stats from your modem here.


ropeguru
Premium
join:2001-01-25
Hollywood, FL
clubs:

reply to SDSuperman
Your hope 13 is just the way they have that router setup to process ICMP requests. The real problem is the link where AT&T hands off to level 3 at hops 11 and 12. Do some pings to hop 12 before and after you see the rise. My guess is that the load is picking up on that link around the time you are seeing the increase. To me, a major link like that should never jump 40ms when they are geographically so close together.


SDSuperman

@bellsouth.net

ropeguru.. there is no before and after now... it's just a solid 60+ and I agree.. I don't think there should be a 40ms jump either. I have ask NFO if they would check into it also and just got a reply back saying that nothing has changed on the NFO network and they would email InterNAP to ask about it.

After just doing a random speed test last night i was getting about a 1/3 of what I should be getting
--> DSL Extreme Download 6 Mbps/512 Kbps Upload
so tonight I'll check it again..


SDSuperman

@bellsouth.net

reply to FastAttack
said by FastAttack See Profile :

level 3 is doing fine even though car2 seems to be high.. it is most likely its priority settings for ping request to that particular router is set to very low...

as a gamer i understand your frustrations but there is really nothing you can do with the peering between level 3 and bellsouth..

but there is something you can do:

1 seems like you are interleave mode adding some latency to your connection.. as you can see in my trace my first hop is 8ms.. which is normal on fastpath connections..

also i noticed some extra hops in your connection, if you are on interleaved + extra hops = higher ping..

maybe its a good idea to tell us what speed package you have and then post your connection stats from your modem here.
FastAttack.. I'm not sure what you wanted but this is a direct connect from pc to dsl modem now.

I don't understand what you mean by "interleave mode adding some latency" and have no idea where to get the modem stats from. As for the the extra hops can anything be done about that?

As for my ISP service I have at&t 6 Mbps down / 512 Kbps up.
I'm actually getting 5.4 Mbps down / 412.9 Kbps up

Speed test








Target Name: c-64-94-238-35.internap-atlanta.nuclearfallout.net
IP: 64.94.238.35
Date/Time: 4/24/2008 10:47:12 PM

1 0 ms 0 ms 0 ms 0 ms 0 ms launchmodem [192.168.1.254]
2 8 ms 8 ms 11 ms 9 ms 9 ms [68.208.232.7]
3 9 ms 9 ms 8 ms 9 ms 9 ms [65.14.199.101]
4 16 ms 16 ms 17 ms 17 ms 17 ms ber00hsv-pos-7-0-0.bellsouth.net [205.152.22.64]
5 17 ms 16 ms 16 ms 17 ms 16 ms ixc01bhm-pos-5-0-0.bellsouth.net [65.83.239.116]
6 16 ms 16 ms 17 ms 16 ms 16 ms ixc00bhm-ge-0-0-0.bellsouth.net [207.203.159.64]
7 16 ms 16 ms 16 ms 16 ms 16 ms [65.83.237.144]
8 15 ms 16 ms 16 ms 16 ms 16 ms axr00aep-ge-5-0-0.bellsouth.net [65.83.238.34]
9 17 ms 16 ms 18 ms 17 ms 16 ms axr01msy-0-3-1.bellsouth.net [65.83.236.31]
10 16 ms 16 ms 17 ms 16 ms 16 ms AXR00AEP-0-1-0.bellsouth.net [65.83.236.50]
11 56 ms 56 ms 56 ms 58 ms 56 ms so-7-0-0.edge1.Atlanta2.Level3.net [4.71.192.21]
12 -32764 ms 58 ms -32764 ms 58 ms 57 ms ae-12-51.car2.Atlanta1.Level3.net [4.68.103.3]
13 57 ms 56 ms 58 ms 57 ms 64 ms internap.level3.net [209.246.169.150]
14 43 ms 43 ms 43 ms 43 ms 42 ms border6.pc2-bbnet2.acs.pnap.net [64.94.0.75]
15 56 ms 56 ms 56 ms 56 ms 56 ms c-64-94-238-35.internap-atlanta.nuclearfallout.net [64.94.238.35]


SDSuperman

@bellsouth.net

 reply to FastAttack


All Entries

CURRENT MODEM STATUS
DSL Modem Status....... Up
PPP Session Status...... Up
Connection Type......... PPPoE
Time set from............. Network
Time since last boot.... 0 days, 1 hrs: 26 mins: 7 secs

Time last modem selftest.. FRI APR 25 17:33:16 2008
Time last modem result.... PASS

EVENTS
**********************************************************************
Events are listed starting from the most recent.
**********************************************************************

FRI APR 25 23:51:31 2008 DNS: Unknown host: '_LDAP._TCP'

FRI APR 25 23:43:12 2008 Setting System clock to Network time FRI APR 25 23:43:12 2008

FRI APR 25 23:43:11 2008 PPP CONNECTED on VPI 8 VCI 35

FRI APR 25 23:43:11 2008 Connecting session(0): My Connection due to AutoConnect request

FRI APR 25 23:43:10 2008 Disconnecting session(-1): due to PADT received

FRI APR 25 23:43:10 2008 PPP DISCONNECTED on VPI 8 VCI 35 : PPP commanded down

FRI APR 25 23:43:10 2008 Disconnecting session(0): My Connection due to dsl Restart

FRI APR 25 23:43:03 2008 US Atten: not defined DS Atten: 18.0

FRI APR 25 23:43:03 2008 US Margin: not defined DS Margin: 14.0

FRI APR 25 23:43:03 2008 US Tx Power: not defined DS Tx Power: not defined

FRI APR 25 23:43:03 2008 US DSL Rate: 512 kbits/sec DS DSL Rate: 7616 kbits/sec

FRI APR 25 23:43:03 2008 WanMgr reports DSL is UP

FRI APR 25 23:42:47 2008 WanMgr reports DSL is Down

FRI APR 25 23:06:11 2008 Setting System clock to Network time FRI APR 25 23:06:11 2008

FRI APR 25 23:06:06 2008 PPP CONNECTED on VPI 8 VCI 35

FRI APR 25 23:06:06 2008 Connecting session(0): My Connection due to dsl Restart

FRI APR 25 23:05:52 2008 US Atten: not defined DS Atten: 18.0

FRI APR 25 23:05:52 2008 US Margin: not defined DS Margin: 15.0

FRI APR 25 23:05:52 2008 US Tx Power: not defined DS Tx Power: not defined

FRI APR 25 23:05:52 2008 US DSL Rate: 512 kbits/sec DS DSL Rate: 7616 kbits/sec

FRI APR 25 23:05:52 2008 WanMgr reports DSL is UP

FRI APR 25 23:05:36 2008 Model Number: B90-210030-04S2

FRI APR 25 23:05:36 2008 Software Version: VER:01.06.64

FRI APR 25 23:05:36 2008 Product: WireSpeed Dual Connect Model: NAT Combo

FRI APR 25 23:05:36 2008 Ethernet A is up : 100 MBps and FULL duplex.

end of diagnostic log file


sojman

@bellsouth.net

reply to ropeguru
said by ropeguru See Profile :

Your hope 13 is just the way they have that router setup to process ICMP requests. The real problem is the link where AT&T hands off to level 3 at hops 11 and 12. Do some pings to hop 12 before and after you see the rise. My guess is that the load is picking up on that link around the time you are seeing the increase. To me, a major link like that should never jump 40ms when they are geographically so close together.
sounds to me that his connection is interleaved.. which is now confirmed by the op
with those stats being marginal as they are , switching from fastpath to interleaved could mean anywhere from 10-15ms added to his routing.

as far as his handoffs again we don't have a prior route to go by. so we should assume the problems from the nid to the rest of the network..

OP i suggest you connect your modem to the nid and get those stats again

variable

join:2002-08-01
Miami, FL


edit:
April 29th, @01:57AM

reply to SDSuperman
no there's definately something wrong with nfo + level 3+ bellsouth(se att) dsl around primetime. It only started maybe a few weeks ago and went away for a little while but it's back. It looks like the nasty latency problems start on the exchange with level3. Confirmed with another friend of mine with bs dsl.

FastAttack
Premium
join:2000-07-28
Fort Lauderdale, FL
clubs:
·AT&T Southeast
·T-Mobile US

said by variable See Profile :

no there's definately something wrong with nfo + level 3+ bellsouth(se att) dsl around primetime. It only started maybe a few weeks ago and went away for a little while but it's back. It looks like the nasty latency problems start on the exchange with level3. Confirmed with another friend of mine with bs dsl.
traceroutes are not a good way to determine network issues ..as ping requests are the bottom of the request priority list for router traffic.

a real test has to be done point to point requests and monitoring the transfer of data to see exactly who is doing the bad handoff..

until then pretty much you as the consumer cant do anything as att is within their TOS


SDSuperman

@bellsouth.net

said by FastAttack See Profile :

said by variable See Profile :

no there's definately something wrong with nfo + level 3+ bellsouth(se att) dsl around primetime. It only started maybe a few weeks ago and went away for a little while but it's back. It looks like the nasty latency problems start on the exchange with level3. Confirmed with another friend of mine with bs dsl.
traceroutes are not a good way to determine network issues ..as ping requests are the bottom of the request priority list for router traffic.

a real test has to be done point to point requests and monitoring the transfer of data to see exactly who is doing the bad handoff..

until then pretty much you as the consumer cant do anything as att is within their TOS
So how can I do that FastAttack? This is a UT2004 gaming server. Anything I can do help resolve this or provide proof where problem is... I can surely try.

variable

join:2002-08-01
Miami, FL

reply to SDSuperman
You're absolutely right, I'm not sure whether the fault lies with att or l3 but it's definately an issue between the two. I have problems with any servers that require transit through level 3 during the peak hours (not just to nfo), but any other routes are completely fine.

Strangely at exactly 10pm all the problems go away. I suppose 50% of all users could go to bed right at the same time thereby eliminating the bottleneck, but it definately feels artificial. Obviously I don't mind them giving icmp lower priority but it seems like they're also throttling gaming or udp packets in general.

And yeah there's nothing we can do about it but complain on a forum

cjskater

join:2008-04-27
Monroe, GA

edit:
May 1st, @11:03PM

reply to SDSuperman
I didn't notice this before but found it googling, I have a post in the Windstream section with the exact same problems. Level3 (in Atlanta at least) is a lot slower now days.

ShadezeRO

join:2006-04-24
Fort Lauderdale, FL
reply to SDSuperman
Best way to check your ping would be in-game.

Also, you're on interleaved, I think those speeds are about right so far. Granted, there could be fluctuations depending on the load to the servers.

variable

join:2002-08-01
Miami, FL
reply to SDSuperman
Is anyone having this problem again? I wonder what the heck is going on? Are they having a spat or something, or maybe we're being filtered/throttled along with torrent traffic?

cjskater

join:2008-04-27
Monroe, GA
I've still got it and ping is terrible today. It's going from 100-190 on a server I normally get 50-60 on.

FastAttack
Premium
join:2000-07-28
Fort Lauderdale, FL
clubs:
·AT&T Southeast
·T-Mobile US

reply to variable
said by variable See Profile :

Is anyone having this problem again? I wonder what the heck is going on? Are they having a spat or something, or maybe we're being filtered/throttled along with torrent traffic?
[/BQUOTE

there is no throttling or shapping of any kind in att dsl

the only port filtered is pop3 for spam reasons..

cjskater, unfortunately it might or might not be the isp , give it a day or so, it might even be the game host isp with the problem.


SDSuperman

@bellsouth.net

 reply to SDSuperman
First time in a long time my ping has been down to 40 in game. Earlier it was as 60 & 56.

Target Name: c-64-94-238-35.internap-atlanta.nuclearfallout.net
IP: 64.94.238.35
Date/Time: 5/13/2008 11:38:20 PM

1 0 ms 0 ms 0 ms 0 ms [192.168.2.1]
2 0 ms 0 ms 0 ms 0 ms [192.168.1.254]
3 9 ms 9 ms 9 ms 9 ms [68.208.232.7]
4 8 ms 10 ms 9 ms 8 ms [65.14.199.101]
5 18 ms 16 ms 16 ms 17 ms ber00hsv-pos-7-0-0.bellsouth.net [205.152.22.64]
6 16 ms 18 ms 16 ms 17 ms ixc01bhm-pos-5-0-0.bellsouth.net [65.83.239.116]
7 17 ms 17 ms 17 ms 16 ms ixc00bhm-ge-0-0-0.bellsouth.net [207.203.159.64]
8 15 ms 16 ms 25 ms 16 ms [65.83.237.144]
9 16 ms 16 ms 17 ms 16 ms axr00aep-ge-5-0-0.bellsouth.net [65.83.238.34]
10 16 ms 17 ms 17 ms 17 ms axr01msy-0-3-1.bellsouth.net [65.83.236.31]
11 16 ms 16 ms 16 ms 16 ms AXR00AEP-0-1-0.bellsouth.net [65.83.236.50]
12 70 ms 43 ms 43 ms 43 ms so-7-1-0.edge1.Atlanta2.Level3.net [4.71.192.9]
13 -32764 ms 45 ms * 44 ms ae-12-51.car2.Atlanta1.Level3.net [4.68.103.3]
14 45 ms 45 ms * 45 ms internap.level3.net [209.246.169.150]
15 44 ms 44 ms 44 ms 43 ms border6.pc2-bbnet2.acs.pnap.net [64.94.0.75]
16 44 ms 43 ms 43 ms 44 ms c-64-94-238-35.internap-atlanta.nuclearfallout.net [64.94.238.35]




Still having problem. Will try to call my ISP and get them to open up a ticket with Level 3 again. If Level 3 tech's are hanging up on anyone else I was told to ask for a manager as soon as the level 3 tech gets online... will try that tomorrow and hope it goes well.

Now on a new motorola 2210 dsl modem. Can not seem to tell if I am on interleaved or fast path with this one. Found on the Westell Wirespeed above if I rebooted it several times sometimes it would change. I could not tell the difference between the two in game or view ping in & out of game.



at&t's speed test show's 4.0 Mbps down & 431.6 Kbps up on 5/14/08 @ 12:24am.




said by FastAttack See Profile
traceroutes are not a good way to determine network issues ..as ping requests are the bottom of the request priority list for router traffic.

a real test has to be done point to point requests and monitoring the transfer of data to see exactly who is doing the bad handoff..

until then pretty much you as the consumer cant do anything as att is within their TOS
[/BQUOTE :


FastAttack... How can the point to point be tested & monitored? Is this something my ISP will be able to do or something I need to do and provide them with the results? Seeing as this is a gaming server I may be allowed to do some sort of file transfer test.

joeblow

join:2007-07-14
Knoxville, TN

reply to SDSuperman
Ill just throw in some history here. I played UT2004 on Cains lair and we had the same problem with Level3 in Atlanta for months. There's always something down there thats a problem.

If I am telling the story correctly the server host pushed a ticket thru Level3 and it worked for a while. I would guess there routers dont like UDP packets.

You could try a whois for the owner of that IP thats the problem and contact them directly. I think ours was some rinky dink company that didnt give a damn and that was most of the problem.

And of course Death Warrent is always open ; )
Forums » US Telco Support » AT&T » AT&T SoutheastWhy did AT&T send me a Motorola 2210 modem? »
« Dry loop DSL with existing POTS and shared DSL  

Most commented news this week
· [122] AT&T WhistleBlower Was Never Invited To Testify
· [53] Comcast Prepared To Spend Big On HD
· [52] Comcast's Use Of Twitter Continues To Fascinate
· [46] Sprint WiMax: Less Than $50
· [39] So Far, 'Franchise Reform' Means Higher Prices
· [31] U-Verse Launches In Tulsa
· [31] Apple Irked With Rogers iPhone Pricing?
· [31] Google: Bell Canada Is Breaking The Law
· [30] NebuAD Tries To Defuse Public Relations Nightmare
· [30] Apple Vs. Rogers: The Fight That Isn't
Wednesday, 09-Jul
01:49:26
Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
8th year online! © 1999-2008 dslreports.com.
page compression OFF