Ping this server

Tek7 (Legacy)

Tek7 (Legacy)

CGA & ToJ President
I've called our first pick for dedicated server hosting and one of their techs gave me this IP address for everyone to ping:

82.165.244.156

Please ping and tracert this IP address and post your results in this thread.

Your results should be a fair indication of the ping you'll get on our game servers if/when we set up an account with this company.

EDIT: Please include your city and state (or just state if you want to remain mysterious) and your connection type (e.g. DSL, cable, dial-up, etc.). Make sure you are not downloading anything when you ping the server.

EDIT: Here are instructions for pinging servers:

Windows 2000/XP users:
  • Click 'Start'
  • Click 'Run'
  • Type cmd and press enter
  • At the command prompt, type ping 82.165.244.156 > ping.txt and press enter.
  • Copy the contents of ping.txt and paste them in your reply to this thread.
Windows 98/Me users:
  • Click 'Start'
  • Click 'Run'
  • Type command and press enter
  • At the command prompt, type ping 82.165.244.156 > ping.txt and press enter.
  • Copy the contents of ping.txt and paste them in your reply to this thread.

Linux users: If you've installed and run Linux, I'm pretty sure you know how to ping a server. :)

EDIT: Here are instructions for running a traceroute on the server:

Windows 2000/XP users:
  • Click 'Start'
  • Click 'Run'
  • Type cmd and press enter
  • At the command prompt, type tracert 82.165.244.156 > tracert.txt and press enter.
  • Copy the contents of tracert.txt and paste them in your reply to this thread.
Windows 98/Me users:
  • Click 'Start'
  • Click 'Run'
  • Type command and press enter
  • At the command prompt, type tracert 82.165.244.156 > tracert.txt and press enter.
  • Copy the contents of tracert.txt and paste them in your reply to this thread.

Linux users: See above note.
 
Last edited:
Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=128ms TTL=54
Reply from 82.165.244.156: bytes=32 time=111ms TTL=54
Reply from 82.165.244.156: bytes=32 time=125ms TTL=54
Reply from 82.165.244.156: bytes=32 time=109ms TTL=54

Ping statistics for 82.165.244.156:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 128ms, Average = 118ms



Tracing route to ns1.1and1root.com [82.165.244.156]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 11 ms 10 ms 10.102.0.1
3 11 ms 14 ms 12 ms click_dtn_ge2-0-0.click-network.com [131.191.27.33]
4 30 ms 22 ms 33 ms t3-1-0-0.ar2.sea1.gblx.net [208.48.250.197]
5 43 ms 35 ms 36 ms so1-1-0-2488m.ar1.sjc2.gblx.net [67.17.64.65]
6 34 ms 33 ms 33 ms 208.50.13.94
7 34 ms 36 ms 36 ms sl-bb21-sj-10-0.sprintlink.net [144.232.20.58]
8 34 ms 34 ms 35 ms sl-bb24-sj-12-0.sprintlink.net [144.232.3.202]
9 38 ms 36 ms 37 ms sl-bb21-stk-12-0.sprintlink.net [144.232.20.180]
10 91 ms 155 ms 106 ms sl-bb26-pen-12-0.sprintlink.net [144.232.20.162]
11 140 ms 95 ms 94 ms sl-bb27-pen-15-0.sprintlink.net [144.232.16.94]
12 94 ms 94 ms 94 ms sl-bb21-nyc-2-0.sprintlink.net [144.232.20.96]
13 92 ms 94 ms 97 ms sl-bb24-nyc-11-0.sprintlink.net [144.232.13.185]
14 96 ms 93 ms 93 ms sl-gw30-nyc-0-0.sprintlink.net [144.232.13.20]
15 109 ms 125 ms 135 ms sl-schlu4-1-0.sprintlink.net [144.232.228.6]
16 117 ms 129 ms 124 ms a0nycc1.gw-core-a.nyc.schlund.net [217.160.229.72]
17 121 ms 145 ms 131 ms ns1.1and1root.com [82.165.244.156]



Trace complete.

Heh, Little higher than first try, average for that long of way clear across US. I'm 40 miles south of Seattle Washington in Tacoma, so yeah, i usually ping 100-110 on GFC custom server. Internet connection at the moment is 2.8Mbits down, 700Kbits up. Once ISP gets upgraded it will be 7Mbits down, 850Kbits up
 
Last edited:
Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=48ms TTL=53
Reply from 82.165.244.156: bytes=32 time=49ms TTL=53
Reply from 82.165.244.156: bytes=32 time=48ms TTL=53
Reply from 82.165.244.156: bytes=32 time=48ms TTL=53

Ping statistics for 82.165.244.156:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 49ms, Average = 48ms

From Ohio !!!
 
Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=39ms TTL=53
Reply from 82.165.244.156: bytes=32 time=39ms TTL=53
Reply from 82.165.244.156: bytes=32 time=39ms TTL=53
Reply from 82.165.244.156: bytes=32 time=39ms TTL=53

Ping statistics for 82.165.244.156:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 39ms, Average = 39ms


U:\>tracert 82.165.244.156

Tracing route to ns1.1and1root.com [82.165.244.156]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 66.210.97.1
2 1 ms 1 ms 1 ms wsip-66-210-216-29.pn.at.cox.net [66.210.216.29]
3 187 ms 199 ms 152 ms 68.1.10.166
4 12 ms 11 ms 11 ms 68.1.15.21
5 11 ms 11 ms 11 ms lkhnbbrc01-pos0101.rd.at.cox.net [68.1.0.4]
6 11 ms 12 ms 12 ms so-1-2-0-0.gar2.atlanta1.level3.net [65.59.222.5]
7 12 ms 12 ms 11 ms ae-1-53.bbr1.atlanta1.level3.net [4.68.103.65]
8 37 ms 30 ms 29 ms as-1-0.bbr2.newyork1.level3.net [64.159.1.85]
9 30 ms 30 ms 32 ms ge-9-0.ipcolo1.newyork1.level3.net [4.68.97.45]
10 39 ms 39 ms 39 ms 4.78.164.2
11 39 ms 39 ms 40 ms a0nycc1.gw-core-a.nyc.schlund.net [217.160.229.72]
12 40 ms 40 ms 43 ms ns1.1and1root.com [82.165.244.156]

Trace complete.
 
Location: St. Louis, MO
Connection: 3Mb cable

Code: 
Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=34ms TTL=51
Reply from 82.165.244.156: bytes=32 time=36ms TTL=51
Reply from 82.165.244.156: bytes=32 time=35ms TTL=51
Reply from 82.165.244.156: bytes=32 time=35ms TTL=51

Ping statistics for 82.165.244.156:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 36ms, Average = 35ms
For some reason, tracert times out on all hops after the first from my machine. It might be related to my router's firewall or security on my PC.

Code: 
Tracing route to ns1.1and1root.com [82.165.244.156]
over a maximum of 30 hops:

  1     9 ms    10 ms    12 ms  10.25.32.1 
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.
 
Last edited:
Ping
Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=45ms TTL=50
Reply from 82.165.244.156: bytes=32 time=43ms TTL=50
Reply from 82.165.244.156: bytes=32 time=42ms TTL=50
Reply from 82.165.244.156: bytes=32 time=43ms TTL=50

Ping statistics for 82.165.244.156:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 45ms, Average = 43ms
Click to expand...
Tracert
Tracing route to ns1.1and1root.com [82.165.244.156]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms home [192.168.1.254]
2 17 ms 17 ms 19 ms ppp-69-221-239-254.dsl.klmzmi.ameritech.net [69.
221.239.254]
3 19 ms 19 ms 19 ms dist2-vlan60.klmzmi.ameritech.net [67.36.55.243]

4 19 ms 19 ms 17 ms bb1-g1-0.klmzmi.ameritech.net [67.36.55.99]
5 22 ms 23 ms 23 ms bb1-p4-2.emhril.ameritech.net [151.164.190.177]

6 22 ms 23 ms 21 ms bb2-p13-0.emhril.ameritech.net [151.164.191.174]

7 23 ms 23 ms 23 ms 151.164.42.141
8 22 ms 23 ms 23 ms chi-bb1-geth6-3-4-0.telia.net [213.248.84.9]
9 43 ms 43 ms 43 ms nyk-bb1-pos0-3-0.telia.net [213.248.80.154]
10 42 ms 43 ms 43 ms nyk-i3-geth1-1.telia.net [213.248.82.146]
11 44 ms 45 ms 45 ms schlund-100973-nyk-i3.c.telia.net [213.248.83.26
]
12 59 ms 210 ms 252 ms a0nycc1.gw-core-a.nyc.schlund.net [217.160.229.7
2]
13 63 ms 45 ms 43 ms ns1.1and1root.com [82.165.244.156]

Trace complete.
Click to expand...


DSL
Western Michigan
 
Tracing route to ns1.1and1root.com [82.165.244.156]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 13 ms 13 ms 13 ms 10.101.96.1
3 10 ms 16 ms 11 ms 68.13.8.114
4 12 ms 12 ms 13 ms 68.13.8.157
5 12 ms 12 ms 11 ms mtc1dsrc01-gew0303.rd.om.cox.net [68.13.14.5]
6 22 ms 26 ms 12 ms 12.125.72.49
7 25 ms 28 ms 27 ms gar1-p370.mpsmn.ip.att.net [12.122.2.218]
8 38 ms 35 ms 31 ms tbr1-p012701.cgcil.ip.att.net [12.122.2.222]
9 28 ms 39 ms 27 ms ggr2-p310.cgcil.ip.att.net [12.123.6.65]
10 29 ms 35 ms 31 ms att-gw.chi.sprint.net [192.205.32.150]
11 27 ms 31 ms 28 ms sl-bb20-chi-4-0.sprintlink.net [144.232.8.218]
12 29 ms 26 ms 28 ms sl-bb21-chi-15-0.sprintlink.net [144.232.26.2]
13 48 ms 63 ms 49 ms sl-bb22-nyc-15-0.sprintlink.net [144.232.9.148]

14 49 ms 47 ms 47 ms sl-bb20-nyc-14-0.sprintlink.net [144.232.7.105]

15 48 ms 48 ms 49 ms sl-bb23-nyc-8-0.sprintlink.net [144.232.7.14]
16 48 ms 57 ms 51 ms sl-gw30-nyc-1-0.sprintlink.net [144.232.13.24]
17 55 ms 56 ms 55 ms sl-schlu4-1-0.sprintlink.net [144.232.228.6]
18 237 ms 250 ms 225 ms a0nycc1.gw-core-a.nyc.schlund.net [217.160.229.7
2]
19 58 ms 56 ms 60 ms ns1.1and1root.com [82.165.244.156]

Trace complete.



Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=58ms TTL=47
Reply from 82.165.244.156: bytes=32 time=71ms TTL=47
Reply from 82.165.244.156: bytes=32 time=57ms TTL=47
Reply from 82.165.244.156: bytes=32 time=57ms TTL=47

Ping statistics for 82.165.244.156:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 71ms, Average = 60ms



From Omaha, NE
 
Last edited:
Location: NE Ohio, USA
Connection: 3 Mbit down, 256 Kbit up

Ping test:
Code: 
Pinging 82.165.244.156 with 32 bytes of data:



Reply from 82.165.244.156: bytes=32 time=21ms TTL=50

Reply from 82.165.244.156: bytes=32 time=24ms TTL=50

Reply from 82.165.244.156: bytes=32 time=24ms TTL=50

Reply from 82.165.244.156: bytes=32 time=25ms TTL=50



Ping statistics for 82.165.244.156:

	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

	Minimum = 21ms, Maximum = 25ms, Average = 23ms

Results of trace route:
Code: 
Tracing route to ns1.1and1root.com [82.165.244.156]

over a maximum of 30 hops:



 1	 1 ms	<1 ms	<1 ms goliath.mshome.net [192.168.1.1] 

 2	 *	 *		*	 Request timed out.

 3	10 ms	11 ms	11 ms acs-72-23-2-229.zoominternet.net [72.23.2.229] 

 4	 *	 14 ms	13 ms acs-72-23-2-193.zoominternet.net [72.23.2.193] 

 5	12 ms	10 ms	12 ms acs-72-23-2-13.zoominternet.net [72.23.2.13] 

 6	11 ms	12 ms	11 ms lco140.zoominternet.net [63.67.120.140] 

 7	11 ms	33 ms	15 ms leg-208-30-204-161-RIA.sprinthome.com [208.30.204.161] 

  8	22 ms	24 ms	23 ms  144.232.13.145 

 9	26 ms	21 ms	24 ms sl-bb24-nyc-10-0.sprintlink.net [144.232.13.181] 

 10	24 ms	24 ms	23 ms sl-gw30-nyc-0-0.sprintlink.net [144.232.13.20] 

 11	27 ms	24 ms	23 ms sl-schlu4-1-0.sprintlink.net [144.232.228.6] 

 12	42 ms	23 ms	23 ms a0nycc1.gw-core-a.nyc.schlund.net [217.160.229.72] 

 13	25 ms	23 ms	24 ms  ns1.1and1root.com [82.165.244.156] 



Trace complete.
 
Last edited:
Code: 
Reply from 82.165.244.156: bytes=32 time=66ms TTL=50
Reply from 82.165.244.156: bytes=32 time=56ms TTL=50
Reply from 82.165.244.156: bytes=32 time=57ms TTL=50
Reply from 82.165.244.156: bytes=32 time=56ms TTL=50

Hey, everybody, look at me! I'm mysterious!

You know where I live anyway. :p
 
Pinging 82.165.244.156 with 32 bytes of data:



Reply from 82.165.244.156: bytes=32 time=100ms TTL=51

Reply from 82.165.244.156: bytes=32 time=77ms TTL=51

Reply from 82.165.244.156: bytes=32 time=117ms TTL=51

Request timed out.



Ping statistics for 82.165.244.156:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 77ms, Maximum = 117ms, Average = 98ms

From Diamond Missouri, really really crappy DSL, i was d/l something at the same time tho, so i dont know if that made a difference.
 
MASH 4077 said:
i was d/l something at the same time tho, so i dont know if that made a difference.
Click to expand...
Aye, that makes a huge difference. Try the ping and tracert commands again when you aren't downloading anything.
 
Location: SW Ohio. USA

Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=41ms TTL=51
Reply from 82.165.244.156: bytes=32 time=49ms TTL=51
Reply from 82.165.244.156: bytes=32 time=42ms TTL=51
Reply from 82.165.244.156: bytes=32 time=39ms TTL=51

Ping statistics for 82.165.244.156:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 49ms, Average = 42ms
Click to expand...

When I do tracert it does one then says operation has times out and puts an *for every where there was a number 1.
 
Testy Testy:

Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=43ms TTL=52
Reply from 82.165.244.156: bytes=32 time=43ms TTL=52
Reply from 82.165.244.156: bytes=32 time=42ms TTL=51
Reply from 82.165.244.156: bytes=32 time=42ms TTL=52

Ping statistics for 82.165.244.156:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 42ms, Maximum = 43ms, Average = 42ms



Tracing route to ns1.1and1root.com [82.165.244.156]

over a maximum of 30 hops:


1 1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 8 ms 11 ms 10.21.76.1
3 13 ms 12 ms 9 ms 12-215-22-129.client.mchsi.com [12.215.22.129]
4 21 ms 23 ms 34 ms 12-215-1-82.client.mchsi.com [12.215.1.82]
5 33 ms 30 ms 23 ms gbr6-p80.cgcil.ip.att.net [12.123.5.222]
6 23 ms 22 ms 22 ms ggr2-p3120.cgcil.ip.att.net [12.123.6.69]
7 22 ms 22 ms 22 ms att-gw.chi.sprint.net [192.205.32.150]
8 23 ms 21 ms 22 ms sl-bb20-chi-4-0.sprintlink.net [144.232.8.218]
9 22 ms 29 ms 24 ms sl-bb21-chi-15-0.sprintlink.net [144.232.26.2]
10 45 ms 42 ms 42 ms sl-bb22-nyc-15-0.sprintlink.net [144.232.9.148]
11 42 ms 50 ms 42 ms sl-bb20-nyc-14-0.sprintlink.net [144.232.7.105]
12 42 ms 80 ms 41 ms sl-bb23-nyc-8-0.sprintlink.net [144.232.7.14]
13 82 ms 45 ms 42 ms sl-gw30-nyc-1-0.sprintlink.net [144.232.13.24]
14 43 ms 44 ms 43 ms sl-schlu4-1-0.sprintlink.net [144.232.228.6]
 
Overall, pings look good so far. Keep postin' those results!

I'll probably call the hosting company tomorrow or Wednesday with more questions.
 
california

Pinging 82.165.244.156 with 32 bytes of data:



Reply from 82.165.244.156: bytes=32 time=95ms TTL=53

Reply from 82.165.244.156: bytes=32 time=95ms TTL=53

Reply from 82.165.244.156: bytes=32 time=94ms TTL=53

Reply from 82.165.244.156: bytes=32 time=95ms TTL=53



Ping statistics for 82.165.244.156:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 94ms, Maximum = 95ms, Average = 94ms

:<
 
Central Ohio
DSL

Code: 
Pinging 82.165.244.156 with 32 bytes of data:
Reply from 82.165.244.156: bytes=32 time=38ms TTL=50
Reply from 82.165.244.156: bytes=32 time=37ms TTL=50
Reply from 82.165.244.156: bytes=32 time=37ms TTL=50
Reply from 82.165.244.156: bytes=32 time=37ms TTL=50
Ping statistics for 82.165.244.156:
	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
	Minimum = 37ms, Maximum = 38ms, Average = 37ms

Code: 
Tracing route to ns1.1and1root.com [82.165.244.156]
over a maximum of 30 hops:
 
1	<1 ms	<1 ms	<1 ms 192.168.1.1 
2	 8 ms	 8 ms	 8 ms adsl-68-250-187-254.dsl.wotnoh.ameritech.net [68.250.187.254] 
3	 9 ms	 9 ms	 9 ms dist1-vlan50.wotnoh.ameritech.net [67.36.13.226] 
4	 9 ms	 9 ms	 9 ms bb1-g8-0.wotnoh.ameritech.net [67.36.13.115] 
5	17 ms	17 ms	17 ms bb1-p4-1.sfldmi.ameritech.net [151.164.190.10] 
6	16 ms	17 ms	17 ms bb2-p15-0.sfldmi.ameritech.net [151.164.40.182] 
7	26 ms	24 ms	24 ms core2-p6-0.crchil.sbcglobal.net [151.164.242.37] 
8	26 ms	25 ms	25 ms 151.164.240.194 
9	26 ms	25 ms	26 ms bb2-p13-0.emhril.ameritech.net [151.164.191.174] 
10	27 ms	27 ms	26 ms ex2-p5-0.eqchil.sbcglobal.net [151.164.42.139] 
11	27 ms	27 ms	27 ms asn1299-telia.eqchil.sbcglobal.net [151.164.250.150] 
12	37 ms	37 ms	37 ms nyk-bb1-pos0-3-0.telia.net [213.248.80.154] 
13	37 ms	37 ms	38 ms nyk-i3-geth1-1.telia.net [213.248.82.146] 
14	37 ms	37 ms	37 ms schlund-100973-nyk-i3.c.telia.net [213.248.83.26] 
15	36 ms	37 ms	38 ms a0nycc1.gw-core-a.nyc.schlund.net [217.160.229.72] 
16	37 ms	37 ms	38 ms ns1.1and1root.com [82.165.244.156]

(I hate how SBC routes me to chicago to go to a server in new york)
 
Ping

Pinging 82.165.244.156 with 32 bytes of data:

Reply from 82.165.244.156: bytes=32 time=126ms TTL=51
Reply from 82.165.244.156: bytes=32 time=134ms TTL=51
Reply from 82.165.244.156: bytes=32 time=115ms TTL=51
Reply from 82.165.244.156: bytes=32 time=124ms TTL=51

Ping statistics for 82.165.244.156:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 134ms, Average = 124ms
Click to expand...


Tracert

Tracing route to ns1.1and1root.com [82.165.244.156]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 30 ms 29 ms 30 ms 70.68.64.1
3 55 ms 29 ms 30 ms rd1bb-ge2-3-1.vc.shawcable.net [64.59.159.146]
4 32 ms 30 ms 29 ms rc1bb-pos15-0.vc.shawcable.net [66.163.69.70]
5 69 ms 35 ms 35 ms rc1wt-pos2-0.wa.shawcable.net [66.163.76.110]
6 53 ms 36 ms 36 ms unknown.Level3.net [63.211.200.29]
7 56 ms 51 ms 53 ms so-7-0-0.mp2.Seattle1.Level3.net [64.159.1.165]
8 99 ms 100 ms 101 ms as-4-0.bbr2.NewYork1.Level3.net [64.159.0.238]
9 100 ms 101 ms 101 ms ge-9-2.ipcolo1.NewYork1.Level3.net [4.68.97.173]
10 142 ms 108 ms 107 ms 4.78.164.2
11 106 ms 113 ms 109 ms a0nycc1.gw-core-a.nyc.schlund.net [217.160.229.72]
12 138 ms 107 ms 106 ms ns1.1and1root.com [82.165.244.156]


Trace complete.
Click to expand...


Le Canada, Colombie Britannique

Câbler l'Internet
 
Plankeye said:
(I hate how SBC routes me to chicago to go to a server in new york)
Click to expand...
dude i hate SBC all together.. i'm trying so hard to get my parents to switch providers.. we just moved and where we were sbc was great.. but here it tottally sucks..my interenet dies on average 15 times a day and on testmy.net were running on 60% of what we pay for and my CS pings have gotten higher.. and the rise in ping only happened a couple of weeks ago.. it's so stupid
 
You must log in or register to reply here.
Back
Top