When everything is running smooth:
C:\Users\xxxxx>hrping www.google.com
This is hrPING v2.44 by cFos Software GmbH -- »
www.cfos.deUsing source IP address 192.168.1.24 to send packets
Pinging www.google.com [173.194.37.80]
with 32 bytes data (60 bytes IP):
Reply from 173.194.37.80: seq=0000 time=30.045ms TTL=54 ID=e07d
Reply from 173.194.37.80: seq=0001 time=31.366ms TTL=54 ID=e07e
Reply from 173.194.37.80: seq=0002 time=31.734ms TTL=54 ID=e07f
Reply from 173.194.37.80: seq=0003 time=31.892ms TTL=54 ID=e080
Statistics for www.google.com:
Packets: sent=4, rcvd=4, error=0, lost=0 (0% loss) in 1.531872 sec
RTTs of replies in ms: min/avg/max/dev: 30.045 / 31.259 / 31.892 / 0.838
C:\Users\xxxxx>tracert www.google.com
Tracing route to www.google.com [173.194.37.51]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 15 ms 15 ms 15 ms adsl-184-38-223-1.msy.bellsouth.net [184.38.223.1]
3 20 ms 18 ms 19 ms 70.159.224.129
4 23 ms 23 ms 24 ms 12.81.24.140
5 19 ms 18 ms 19 ms 12.81.24.97
6 19 ms 18 ms 18 ms 74.175.192.26
7 35 ms 32 ms 31 ms cr1.nwrla.ip.att.net [12.123.153.18]
8 34 ms 36 ms 36 ms cr2.attga.ip.att.net [12.122.18.1]
9 31 ms 31 ms 31 ms 12.122.140.185
10 32 ms 31 ms 31 ms 12.91.100.214
11 32 ms 32 ms 32 ms 64.233.174.2
12 34 ms 33 ms 33 ms 64.233.175.92
13 32 ms 33 ms 33 ms atl14s07-in-f19.1e100.net [173.194.37.51]
Trace complete.
When I have problems(mostly at night):
C:\Users\xxxxx>hrping www.google.com
This is hrPING v2.44 by cFos Software GmbH -- »
www.cfos.deUsing source IP address 192.168.1.24 to send packets
Pinging www.google.com [74.125.130.106]
with 32 bytes data (60 bytes IP):
Reply from 74.125.130.106: seq=0000 time=81.224ms TTL=47 ID=600a
Reply from 74.125.130.106: seq=0001 time=76.871ms TTL=47 ID=600b
Reply from 74.125.130.106: seq=0002 time=76.484ms TTL=47 ID=600c
Reply from 74.125.130.106: seq=0003 time=72.473ms TTL=47 ID=600d
Statistics for www.google.com:
Packets: sent=4, rcvd=4, error=0, lost=0 (0% loss) in 1.572476 sec
RTTs of replies in ms: min/avg/max/dev: 72.473 / 76.763 / 81.224 / 3.577
C:\Users\xxxxx>tracert www.google.com
Tracing route to www.google.com [74.125.130.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 15 ms 15 ms 14 ms adsl-184-38-223-1.msy.bellsouth.net [184.38.223.1]
3 66 ms 64 ms 67 ms 70.159.224.131
4 62 ms 60 ms 66 ms 12.81.24.50
5 64 ms 117 ms 62 ms 12.81.24.35
6 * 55 ms 58 ms 74.175.192.26
7 80 ms 80 ms 78 ms cr1.nwrla.ip.att.net [12.123.153.18]
8 110 ms 83 ms 76 ms cr2.attga.ip.att.net [12.122.18.1]
9 86 ms 208 ms 95 ms 12.122.140.185
10 74 ms 69 ms 72 ms 12.91.100.214
11 78 ms 75 ms 75 ms 72.14.239.100
12 75 ms 75 ms 78 ms 66.249.94.20
13 77 ms 88 ms 71 ms 209.85.254.249
14 * * * Request timed out.
15 79 ms 77 ms 78 ms gh-in-f99.1e100.net [74.125.130.99]
Trace complete.
I have 6mb DSL in a very rural area. There is some kind of repeater between local customers and nearest CO. I would like to know what is the adsl-184-38-223-1.msy.bellsouth.net? This has only popped up recently and seems to be the source of my issue. I only connect with 184.???.xxx.xxx ip addresses now. Before this I would get 7x.xxx.xxx.xxx, or 6x.xxx.xxx.xxx ip addresses and was never routed through this ADSL gateway thing(w/e it is). Did at&t add something that makes me share my line? I know only a couple hundred people can be on our box and supposedly no new customers are added. My brother is a line tech for at&t but he is unfamilar with these advanced networking issues. I play competitive FPS on an almost professional level, so this is a problem for me.