Author Topic: new server pingplot ugh! (Read 572 times)

used2bz · « **on:** February 28, 2006, 09:35:16 PM »

Here's my pingplot to new server from MI

Target Name: argon.gamerslobby.net
IP: 206.123.111.42
Date/Time: 2/28/2006 10:34:41 PM

1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.0.1]
2 8 ms 10 ms 16 ms 7 ms 7 ms 9 ms 9 ms 7 ms 10 ms 6 ms [73.42.4.1]
3 8 ms 6 ms 9 ms 7 ms 9 ms 9 ms 5 ms 7 ms 6 ms 7 ms [12.244.250.177]
4 22 ms 16 ms 11 ms 14 ms 13 ms 11 ms 12 ms 14 ms 13 ms 14 ms [12.118.112.9]
5 41 ms 41 ms 41 ms 43 ms 40 ms 66 ms 46 ms 45 ms 41 ms 42 ms tbr1-p012401.dtrmi.ip.att.net [12.123.139.53]
6 45 ms 44 ms 42 ms 44 ms 42 ms 45 ms 43 ms 41 ms 43 ms 44 ms tbr1-cl28.sl9mo.ip.att.net [12.122.12.186]
7 42 ms 44 ms 43 ms 41 ms 44 ms 41 ms 44 ms 42 ms 64 ms 43 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
8 42 ms 44 ms 43 ms 53 ms 43 ms 41 ms 53 ms 42 ms 41 ms 42 ms gar1-p370.dlrtx.ip.att.net [12.123.196.97]
9 * * * * * * * * * * [-]
10 42 ms 44 ms 46 ms 44 ms 45 ms 43 ms 44 ms 42 ms 43 ms 44 ms border4.ge4-1-bbnet2.ext1.dal.pnap.net [216.52.191.94]
11 43 ms 44 ms 42 ms 42 ms 45 ms 45 ms 45 ms 43 ms 42 ms 42 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.189.10]
12 42 ms 46 ms 43 ms 46 ms 44 ms 41 ms 42 ms 45 ms 47 ms 43 ms [206.123.64.38]
13 44 ms 43 ms 46 ms 44 ms 46 ms 46 ms 43 ms 46 ms 44 ms * [206.123.64.98]
14 44 ms 45 ms 44 ms 44 ms 42 ms 42 ms 42 ms 41 ms 43 ms 43 ms argon.gamerslobby.net [206.123.111.42]

zrex

StarOfAfrica2 · « **Reply #1 on:** March 01, 2006, 10:53:14 AM »

What exactly are you trying to say? That its bad? Except for hop 9 thats actually pretty good.

feem · « **Reply #2 on:** March 01, 2006, 03:53:22 PM »

Many routers either grant a lower priority to ICMP traffic or fail to respond to ICMP echo requests. Hop 9's results are not uncommon.

Skuzzy · « **Reply #3 on:** March 01, 2006, 04:07:06 PM »

Correct. Hop 9 happens to ignore ICMP ECHO messages.

feem · « **Reply #4 on:** March 01, 2006, 04:40:40 PM »

Hi Roy.

used2bz · « **Reply #5 on:** March 01, 2006, 06:33:08 PM »

Thanks for info. I saw hop 9 and thought I was screwed. It was showing 100% packet loss. How can you tell what hops are like this one? I didn't have time to play when I did the plot , but everything was fine when I tried this morning, including ping plot.

zrex

feem · « **Reply #6 on:** March 01, 2006, 06:38:00 PM »

If a router is actually experiencing dropped packets, in repeated traceroutes/plots it will generally fluctuate. It may be * * time, or * time *, or even ***, but the important thing to notice is the perceived source of the problem over the course of several plots.

That is, any hop which is actually dropping packets and experiencing packetloss will generally affect every subsequent hop in the trace.

Watch for ping spikes that are sustained across several hops (and are significant or exponential, rather than the expected 30-60ms hop for a geographical distance, i.e. virginia to texas or michigan to california, or overseas to usa) and packetloss which represents itself across one hop and every significant hop thereafter.

If it's a single hop or a few hops that show as blanks but everything after that hop is pinging fine, you're probably fine too.

used2bz · « **Reply #7 on:** March 01, 2006, 06:44:35 PM »

Got it. Thanks Feem

zrex