Higher Than Usual Ping

[ijag]

Ok...I have gone to .....The Planet Forums

See what I can get out of there.

Check out my latest trace.

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     8 ms    23 ms     8 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4    11 ms     7 ms    10 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5     7 ms    17 ms     9 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    39 ms    40 ms    43 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7   102 ms   101 ms   101 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8   142 ms   140 ms   142 ms  70.87.253.194
  9   141 ms   143 ms   159 ms  70.87.253.26
 10   137 ms   138 ms   145 ms  te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
11   180 ms   149 ms   161 ms  12.96.160.40
 12   137 ms   139 ms   137 ms  tastyspleen.net [74.54.186.226]

Trace complete.


Whats up with marked lines......why are they just ip's??

[reaper]

no reverse dns record for that IP.

you could try pathping for better stats, same as traceroute but type pathping. the packets with expiered ttl values are handled different than normal, by hops.  Why you see a higher ping time halfway there than to the destination.  You could ping a host on the attached subnet for a beter indication of what's up, if the traceroute isn't obvious.

[ijag]

I tried pathping, but I am not sure what this means. It does 2 hops then calculates. for awhile. But here it is anyhow.

I also wanted to say, I ping 15 at the West Coast U.S. OPENTDM server.


here's my pathping

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  0  mypc.vn.shawcable.net [192.168.1.100]
  1  192.168.1.1
  2     *        *        *
Computing statistics for 50 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           madman-pc.vn.shawcable.net [192.168.1.100]                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1                                                             100/ 100 =100%   |
  2  ---     100/ 100 =100%     0/ 100 =  0%  madman-pc [0.0.0.0]

Trace complete.

[reaper]

It looks like ICMP is being blocked, you can ping the server and run traceroutes? which traceroute are you using?

[ijag]

Do you mean to ping each server that I see in my trace ?

I used cmd>tracert tastyspleen.net for this one,


Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     8 ms     8 ms     9 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4     9 ms    10 ms     9 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5     8 ms     9 ms     9 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    40 ms    43 ms    40 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7   103 ms   101 ms    99 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8   143 ms   141 ms   141 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  9   141 ms   142 ms   141 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
 10   138 ms   138 ms   137 ms  te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
 11   144 ms   141 ms   150 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 12   137 ms   137 ms   138 ms  tastyspleen.net [74.54.186.226]

Trace complete.
----------------------------------------

This one useing cmd>pathping tastyspleen.net

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:
  0  mypc.vn.shawcable.net [192.168.1.102]
  1  192.168.1.1
  2     *        *        *
Computing statistics for 50 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           mypc.vn.shawcable.net [192.168.
1.102]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                              100/ 100 =100%   |
  2  ---     100/ 100 =100%     0/ 100 =  0%  mypc [0.0.0.0]

Trace complete.

[Pr0c3550r]

THE PLANET

[Vigilante]

You Shaw cable people seem to be having the same issue I was a week ago.

The problem you see when pings jump that high from one hop to another are usually a result of asymetrical routing. For instance in my case, my ISP peers with the Planet in Dallas and in Ashburn, VA.

My forward route would go to Dallas as it should, but since there are 2 peering points The Planet was thinking that the return path back through Ashburn was the better route.  That explained my high pings because it was going through Ashburn on the reply to my traceroute back to me.

In my case since I had a server at the planet so I was able to open a trouble ticket on my issue at The Planet and they were able to correct it. I would just hit up either your provider to see if they turned up any new peering points with The Planet or have Tastyspleen check with The Planet to see if they peer with your ISP in more than one location.

The key is mapping out the return path, since I work in the NOC at my ISP I was able to sinply log into our gear and see where the return traffic was coming in at. I'm not saying this is for sure what the issue is, but it definately sounds like it.

[ijag]

So how would someone in my situation make this happen?
Or can I?   lol

I am a little shocked as to my game play, at least on my computer. I am actually doing pretty good, nothing like running around in the West Coast Server tho......when I hit the button to fire...it fires like right now....thats always nice 

I seem to have good and bad as we all do. So I am just gonna ride this out for a little while and keep hairy assing them fine folks at Shaw.
I will of course keep trying to figure this out as well in here with all you upstanding individuals.

[Pr0c3550r]

yeah, I ping a sweet 15 @ the West Coast Server 

[bio]

  1     5 ms    10 ms     4 ms  router.bio.homeunix.com [192.168.1.3]
  2    16 ms    10 ms    13 ms  gda-ru3.neo.tpnet.pl [213.25.2.61]
  3    10 ms    15 ms    11 ms  ge-1-1-2.gda-r1.tpnet.pl [212.160.0.5]
  4    27 ms    24 ms    18 ms  194.204.175.89
  5    44 ms    43 ms    44 ms  pos0-6-0-0.ffttr1.FrankfurtAmMain.opentransit.net [193.251.250.113]
  6    41 ms    44 ms    40 ms  64.208.110.225
  7   166 ms   160 ms   162 ms  The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net[64.208.170.198]
  8   161 ms   164 ms   171 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
  9   236 ms   169 ms   161 ms  te3-3.dsr02.dllstx2.theplanet.com [70.87.253.126]
 10   252 ms   182 ms   179 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 11   160 ms   160 ms   166 ms  tastyspleen.net [74.54.186.226]

Either France Telecom or Global Crossing... Transocean link SUCKS. They give us this "physical-barrier-speed-of-light" crap :/ Not to mention policy based routing of France Telecom - they put all traffic from Middle East Europe to this shitty Global Crossing GE port (almost all trafic from our country ends up there), and use their QoS link for traffic originating from their AS (and "buddy" AS-es). This sucks man...

'cose of this shit, can't own all rounds

[Krazy]

Hey bio, you and I have the same "problem". I connect from belgium and you from france.

My problem starts here:
 6    12 ms    10 ms     9 ms  te3-2.ar1.NLD1.ANT1.gblx.net [64.215.184.29]
  7   137 ms   137 ms   136 ms  The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net
[64.208.170.198]

And yours here:
 6    41 ms    44 ms    40 ms  64.208.110.225
  7   166 ms   160 ms   162 ms  The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net[64.208.170.198]

So I think it's the transatlantic connection.

My return trace from ts is very different though. Which is more important the to trace or the from trace?

And most important.. What can ze DO about it like Vigilante?

[ijag]

Just wanted to say Thanks to all for the help on this.

[ijag]

Just got off the phone with shaw after being on hold for 20 minutes, 10 before they answered and 10 after they answered, and so...they say they can not do a thing about it.  Nice.

[sinner]

Well for some reason my ping came back to normal yesterday!! I pinged 63 instead of 100/105 so thats good news.

I didnt do anything, just came back to normal, thats good news, hope it lasts!

[X7]

Visual trace route tool displays the path Internet packets traverse to reach a specified destination.
http://www.yougetsignal.com/tools/visual-tracert/

Here is trace route with 20 hops & 8,443 miles traveled,
I get a 40 ping on the TS servers.





X7