Ask a question
Search in Internet Forums

Internet Forum

Reply
Posted Jan 27, 2011
7:57:56 AM
Ping / Routing Issue!

My ping has jumped from 38 to 95 everywhere on the east coast.  I have a friend down the road and one in the next county with the same issue.  Just started a day or two ago.  Sorry I don't have any info as far as traceroutes to provide at this time.  If I need to do so please let me know.  Any help would be appreciated.

My ping has jumped from 38 to 95 everywhere on the east coast.  I have a friend down the road and one in the next county with the same issue.  Just started a day or two ago.  Sorry I don't have any info as far as traceroutes to provide at this time.  If I need to do so please let me know.  Any help would be appreciated.

Ping / Routing Issue!

1,454 views
6 replies
(0) Me too
(0) Me too
Reply
View all replies
(6)
0
(0)
  • Rate this reply
View profile
Jan 27, 2011 10:07:40 PM
0
(0)
Tutor

after doing the tracert, it looks like the level3.net is where the problem is.  their numbers are way higher than the rest.

after doing the tracert, it looks like the level3.net is where the problem is.  their numbers are way higher than the rest.

Re: Ping / Routing Issue!

2 of 7 (1,398 Views)
0
(0)
  • Rate this reply
View profile
Jan 27, 2011 10:16:35 PM
0
(0)
Tutor

Target Name: N/A
         IP: 69.12.54.12
  Date/Time: 1/28/2011 1:13:21 AM

 1    1 ms    1 ms    1 ms    0 ms    1 ms    0 ms  home [192.168.1.254]
 2   12 ms   13 ms   12 ms   13 ms   12 ms   13 ms  [68.152.231.134]
 3   12 ms   15 ms   12 ms   12 ms   11 ms   10 ms  [68.152.231.145]
 4   22 ms   23 ms   19 ms   19 ms   21 ms   19 ms  [12.81.40.36]
 5   21 ms   22 ms   20 ms   23 ms   20 ms   27 ms  [12.81.104.48]
 6   21 ms   41 ms   20 ms   20 ms   22 ms   21 ms  BER01BCT-4-0.bellsouth.net [65.83.237.103]
 7   21 ms   19 ms   19 ms   21 ms   19 ms   20 ms  [12.81.46.5]
 8   23 ms   21 ms   23 ms   21 ms   23 ms   21 ms  [12.81.56.6]
 9   19 ms   22 ms   83 ms   20 ms   20 ms   21 ms  [12.81.56.17]
10   29 ms   28 ms   23 ms   24 ms   94 ms   24 ms  [65.83.238.186]
11   36 ms   39 ms   39 ms   39 ms   35 ms   40 ms  cr2.rlgnc.ip.att.net [12.123.152.110]
12   39 ms   36 ms   35 ms   40 ms   40 ms   35 ms  cr1.wswdc.ip.att.net [12.122.3.170]
13   34 ms   36 ms   49 ms   34 ms   31 ms   34 ms  wswdc02jt.ip.att.net [12.122.88.173]
14   37 ms   41 ms   35 ms   37 ms   35 ms   33 ms  xe-6-1-0.edge1.Washington4.level3.net [4.68.62.29]
15   33 ms   38 ms   35 ms   39 ms   40 ms   35 ms  vlan51.ebr1.Washington12.Level3.net [4.69.146.190]
16   29 ms   40 ms   40 ms   36 ms   44 ms   42 ms  ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
17   30 ms   29 ms   29 ms   30 ms   29 ms   30 ms  ae-71-71.csw2.Atlanta2.Level3.net [4.69.148.246]
18   30 ms   30 ms   35 ms   29 ms   45 ms   29 ms  ae-22-52.car2.Atlanta1.Level3.net [4.69.150.68]
19   94 ms   86 ms   93 ms   93 ms   93 ms   96 ms  unknown.Level3.net [63.210.88.154]
20   92 ms   94 ms   94 ms   93 ms   92 ms   93 ms  [69.12.54.12]

Ping statistics for 69.12.54.12
Packets: Sent = 6, Received = 6, Lost = 0 (0.0%)
Round Trip Times: Minimum = 92ms, Maximum = 94ms, Average = 93ms

Target Name: N/A
         IP: 69.12.54.12
  Date/Time: 1/28/2011 1:13:21 AM

 1    1 ms    1 ms    1 ms    0 ms    1 ms    0 ms  home [192.168.1.254]
 2   12 ms   13 ms   12 ms   13 ms   12 ms   13 ms  [68.152.231.134]
 3   12 ms   15 ms   12 ms   12 ms   11 ms   10 ms  [68.152.231.145]
 4   22 ms   23 ms   19 ms   19 ms   21 ms   19 ms  [12.81.40.36]
 5   21 ms   22 ms   20 ms   23 ms   20 ms   27 ms  [12.81.104.48]
 6   21 ms   41 ms   20 ms   20 ms   22 ms   21 ms  BER01BCT-4-0.bellsouth.net [65.83.237.103]
 7   21 ms   19 ms   19 ms   21 ms   19 ms   20 ms  [12.81.46.5]
 8   23 ms   21 ms   23 ms   21 ms   23 ms   21 ms  [12.81.56.6]
 9   19 ms   22 ms   83 ms   20 ms   20 ms   21 ms  [12.81.56.17]
10   29 ms   28 ms   23 ms   24 ms   94 ms   24 ms  [65.83.238.186]
11   36 ms   39 ms   39 ms   39 ms   35 ms   40 ms  cr2.rlgnc.ip.att.net [12.123.152.110]
12   39 ms   36 ms   35 ms   40 ms   40 ms   35 ms  cr1.wswdc.ip.att.net [12.122.3.170]
13   34 ms   36 ms   49 ms   34 ms   31 ms   34 ms  wswdc02jt.ip.att.net [12.122.88.173]
14   37 ms   41 ms   35 ms   37 ms   35 ms   33 ms  xe-6-1-0.edge1.Washington4.level3.net [4.68.62.29]
15   33 ms   38 ms   35 ms   39 ms   40 ms   35 ms  vlan51.ebr1.Washington12.Level3.net [4.69.146.190]
16   29 ms   40 ms   40 ms   36 ms   44 ms   42 ms  ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
17   30 ms   29 ms   29 ms   30 ms   29 ms   30 ms  ae-71-71.csw2.Atlanta2.Level3.net [4.69.148.246]
18   30 ms   30 ms   35 ms   29 ms   45 ms   29 ms  ae-22-52.car2.Atlanta1.Level3.net [4.69.150.68]
19   94 ms   86 ms   93 ms   93 ms   93 ms   96 ms  unknown.Level3.net [63.210.88.154]
20   92 ms   94 ms   94 ms   93 ms   92 ms   93 ms  [69.12.54.12]

Ping statistics for 69.12.54.12
Packets: Sent = 6, Received = 6, Lost = 0 (0.0%)
Round Trip Times: Minimum = 92ms, Maximum = 94ms, Average = 93ms

Re: Ping / Routing Issue!

3 of 7 (1,396 Views)
0
(0)
  • Rate this reply
View profile
Jan 28, 2011 9:07:07 PM
0
(0)
Tutor

Can anyone tell me why the couple of bad hops at the end cause my ping to be the same in games?  I play quake live and usually ping 38 to atlanta servers which is the ip of the last hop.  last couple of days it has been in the 80-90's.  same goes for my buddies.  I hope this issue will be resolved asap, 90 ping is unacceptable for gaming.  im a loyal dsl customer for about 10 years, a little help would be appreciated.

Can anyone tell me why the couple of bad hops at the end cause my ping to be the same in games?  I play quake live and usually ping 38 to atlanta servers which is the ip of the last hop.  last couple of days it has been in the 80-90's.  same goes for my buddies.  I hope this issue will be resolved asap, 90 ping is unacceptable for gaming.  im a loyal dsl customer for about 10 years, a little help would be appreciated.

Re: Ping / Routing Issue!

4 of 7 (1,365 Views)
0
(0)
  • Rate this reply
View profile
Jan 28, 2011 9:22:37 PM
0
(0)
Mentor

I just ran a tracert to 69.12.54.12 and it looks like that Level3 is the problem.

 

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Crash>tracert 69.12.54.12

Tracing route to 69.12.54.12 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  READYSHARE [10.0.0.1]
  2     8 ms     8 ms     8 ms  70.159.160.16
  3    10 ms    10 ms    10 ms  70.159.176.52
  4     9 ms     9 ms     9 ms  70.159.176.82
  5    10 ms     9 ms     9 ms  12.81.16.2
  6     9 ms     9 ms     8 ms  12.81.16.7
  7    10 ms     9 ms    10 ms  74.175.192.74
  8    12 ms    11 ms    11 ms  cr1.attga.ip.att.net [12.122.141.186]
  9   145 ms    74 ms    10 ms  attga04jt.ip.att.net [12.122.84.113]
 10    10 ms    10 ms    10 ms  192.205.35.218
 11    54 ms    43 ms    10 ms  ae-22-52.car2.Atlanta1.Level3.net [4.69.150.68]

 12    66 ms    70 ms    66 ms  unknown.Level3.net [63.210.88.154]
 13    67 ms    66 ms    66 ms  69.12.54.12

Trace complete.

 

One to google.com

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Crash>tracert google.com

Tracing route to google.com [74.125.65.106]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  READYSHARE [10.0.0.1]
  2     8 ms     8 ms     8 ms  70.159.160.16
  3    10 ms    10 ms    10 ms  70.159.176.52
  4     9 ms     9 ms     9 ms  70.159.176.82
  5    10 ms    10 ms    10 ms  12.81.16.30
  6     9 ms     9 ms     8 ms  12.81.16.25
  7    10 ms    10 ms    10 ms  74.175.192.62
  8    12 ms    12 ms    11 ms  cr2.attga.ip.att.net [12.122.140.186]
  9    10 ms    10 ms    10 ms  12.123.22.129
 10    11 ms    11 ms    10 ms  12.88.97.6
 11    11 ms    10 ms    10 ms  72.14.233.54
 12    12 ms    11 ms    12 ms  72.14.239.131
 13    21 ms    15 ms    20 ms  209.85.253.209
 14    12 ms    12 ms    12 ms  gx-in-f106.1e100.net [74.125.65.106]

Trace complete.

 

If you're looking/waiting for a response from someone at AT&T here, don't hold your breath. Best you'll get from them is the same script you get with a phone call.

I just ran a tracert to 69.12.54.12 and it looks like that Level3 is the problem.

 

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Crash>tracert 69.12.54.12

Tracing route to 69.12.54.12 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  READYSHARE [10.0.0.1]
  2     8 ms     8 ms     8 ms  70.159.160.16
  3    10 ms    10 ms    10 ms  70.159.176.52
  4     9 ms     9 ms     9 ms  70.159.176.82
  5    10 ms     9 ms     9 ms  12.81.16.2
  6     9 ms     9 ms     8 ms  12.81.16.7
  7    10 ms     9 ms    10 ms  74.175.192.74
  8    12 ms    11 ms    11 ms  cr1.attga.ip.att.net [12.122.141.186]
  9   145 ms    74 ms    10 ms  attga04jt.ip.att.net [12.122.84.113]
 10    10 ms    10 ms    10 ms  192.205.35.218
 11    54 ms    43 ms    10 ms  ae-22-52.car2.Atlanta1.Level3.net [4.69.150.68]

 12    66 ms    70 ms    66 ms  unknown.Level3.net [63.210.88.154]
 13    67 ms    66 ms    66 ms  69.12.54.12

Trace complete.

 

One to google.com

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Crash>tracert google.com

Tracing route to google.com [74.125.65.106]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  READYSHARE [10.0.0.1]
  2     8 ms     8 ms     8 ms  70.159.160.16
  3    10 ms    10 ms    10 ms  70.159.176.52
  4     9 ms     9 ms     9 ms  70.159.176.82
  5    10 ms    10 ms    10 ms  12.81.16.30
  6     9 ms     9 ms     8 ms  12.81.16.25
  7    10 ms    10 ms    10 ms  74.175.192.62
  8    12 ms    12 ms    11 ms  cr2.attga.ip.att.net [12.122.140.186]
  9    10 ms    10 ms    10 ms  12.123.22.129
 10    11 ms    11 ms    10 ms  12.88.97.6
 11    11 ms    10 ms    10 ms  72.14.233.54
 12    12 ms    11 ms    12 ms  72.14.239.131
 13    21 ms    15 ms    20 ms  209.85.253.209
 14    12 ms    12 ms    12 ms  gx-in-f106.1e100.net [74.125.65.106]

Trace complete.

 

If you're looking/waiting for a response from someone at AT&T here, don't hold your breath. Best you'll get from them is the same script you get with a phone call.

Re: Ping / Routing Issue!

5 of 7 (1,361 Views)
0
(0)
  • Rate this reply
View profile
Feb 25, 2011 12:38:52 PM
0
(0)
Former Moderator

Hello mkdobson3,

 

Please accept my sincere apologies for I find your issue a bit vague.

However, let me just give you a brief description on how to differentiate a good tracert from a bad tracert.

 

A good traceroute:

 

As the packets travel from point A to point B, each hop appear on its own line. Traceroute should display the address and name of each server/router/node along the way and the amount of time (measured in

milliseconds) the packets take to travel on each hop between point A to point B.

 

A bad traceroute:

 

Each line of the traceroute displays three (3) pings and the server/router/node of that hop. Asterisks (* * *) found in the hops indicate a timeout. If you see a line with just asterisks on it, that means that the hop between server/router/node took longer than 200ms.

Several lines of timeouts mean the packets are being held up, clogged or lost somewhere along the way. An average good response is around 1ms to 80ms. Any response above 300ms could potentially affect traffic through that hop and would be considered a bad response. If consistent timeouts or bad responses are found within the AT&T network hops, this an AT&T issue. If consistent timeouts or bad responses are found outside of the AT&T network hops, this is not an AT&T issue.

 

 

NOTE: Some points on the traceroute will show a timeout because administrators have restricted pings. This may not necessarily indicate a fail point. If the destination host is not reachable at all, then failures will typically be sporadic: * 200ms * (2 timeouts and 1 successful).

 

Should you need further help regarding your post, please feel free to reply on this thread.

 

For additional assistance, you may chat us by accessing this link:

https://pattta.att.motive.com/netagent/questionnaire_c2c_dsl_se.aspx

Remember to always mark items that you find useful as "Accepted Solutions”, you can even mark multiple
posts
in a single thread.  This will help other users find this information too!!

Hello mkdobson3,

 

Please accept my sincere apologies for I find your issue a bit vague.

However, let me just give you a brief description on how to differentiate a good tracert from a bad tracert.

 

A good traceroute:

 

As the packets travel from point A to point B, each hop appear on its own line. Traceroute should display the address and name of each server/router/node along the way and the amount of time (measured in

milliseconds) the packets take to travel on each hop between point A to point B.

 

A bad traceroute:

 

Each line of the traceroute displays three (3) pings and the server/router/node of that hop. Asterisks (* * *) found in the hops indicate a timeout. If you see a line with just asterisks on it, that means that the hop between server/router/node took longer than 200ms.

Several lines of timeouts mean the packets are being held up, clogged or lost somewhere along the way. An average good response is around 1ms to 80ms. Any response above 300ms could potentially affect traffic through that hop and would be considered a bad response. If consistent timeouts or bad responses are found within the AT&T network hops, this an AT&T issue. If consistent timeouts or bad responses are found outside of the AT&T network hops, this is not an AT&T issue.

 

 

NOTE: Some points on the traceroute will show a timeout because administrators have restricted pings. This may not necessarily indicate a fail point. If the destination host is not reachable at all, then failures will typically be sporadic: * 200ms * (2 timeouts and 1 successful).

 

Should you need further help regarding your post, please feel free to reply on this thread.

 

For additional assistance, you may chat us by accessing this link:

https://pattta.att.motive.com/netagent/questionnaire_c2c_dsl_se.aspx

Remember to always mark items that you find useful as "Accepted Solutions”, you can even mark multiple
posts
in a single thread.  This will help other users find this information too!!

Re: Ping / Routing Issue!

6 of 7 (1,012 Views)
0
(0)
  • Rate this reply
View profile
Sep 14, 2011 5:29:54 AM
0
(0)
Teacher
Edited by sweety7 on Sep 14, 2011 at 5:30:34 AM

i tried ping test here whoisxy.com my results areReply from 173.203.189.224: bytes=32 time<1ms TTL=128Reply from 173.203.189.224: bytes=32 time<1ms TTL=128Reply from 173.203.189.224: bytes=32 time<1ms TTL=128Reply from 173.203.189.224: bytes=32 time<1ms TTL=128Ping statistics for 173.202.190.224Smiley Tongueackets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 0ms, Maximum = 0ms, Average = 0ms

i tried ping test here whoisxy.com my results areReply from 173.203.189.224: bytes=32 time<1ms TTL=128Reply from 173.203.189.224: bytes=32 time<1ms TTL=128Reply from 173.203.189.224: bytes=32 time<1ms TTL=128Reply from 173.203.189.224: bytes=32 time<1ms TTL=128Ping statistics for 173.202.190.224Smiley Tongueackets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 0ms, Maximum = 0ms, Average = 0ms

Re: Ping / Routing Issue!

[ Edited ]
7 of 7 (753 Views)
Advanced
You must be signed in to add attachments
Share this post
Share this post