Upvote Upvoted 4 Downvote Downvoted
Check pings to those servers!
posted in Off Topic
1
#1
3 Frags +

#1: 95.47.119.2 (Amsterdam, The Netherlands)
#2: 176.56.238.3 (Alblasserdam, The Netherlands)

Please don't forget to include your location. I'm mainly interested in EU players but I don't mind couple NA results. If you could even add couple traceroutes that would be pretty much awesome. I've already talked to several people on Steam and I managed to gather several results which all of them are published here (for those interested): https://docs.google.com/spreadsheet/ccc?key=0AtWijEJCERMAdC03M3F4YzZWemhwQzJBcUFhZDFqMHc

Thank you.

#1: 95.47.119.2 (Amsterdam, The Netherlands)
#2: 176.56.238.3 (Alblasserdam, The Netherlands)

Please don't forget to include your location. I'm mainly interested in EU players but I don't mind couple NA results. If you could even add couple traceroutes that would be pretty much awesome. I've already talked to several people on Steam and I managed to gather several results which all of them are published here (for those interested): https://docs.google.com/spreadsheet/ccc?key=0AtWijEJCERMAdC03M3F4YzZWemhwQzJBcUFhZDFqMHc

Thank you.
2
#2
1 Frags +

Location: London

https://dl.dropboxusercontent.com/u/29256607/pings2.png

Location: London

[img]https://dl.dropboxusercontent.com/u/29256607/pings2.png[/img]
3
#3
0 Frags +

That's pretty good. Thank you.

That's pretty good. Thank you.
4
#4
1 Frags +

Location: Europe, Lithuania.

Pinging 95.47.119.2 with 32 bytes of data:
Reply from 95.47.119.2: bytes=32 time=45ms TTL=55
Reply from 95.47.119.2: bytes=32 time=44ms TTL=55
Reply from 95.47.119.2: bytes=32 time=44ms TTL=55
Reply from 95.47.119.2: bytes=32 time=44ms TTL=55

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

-------------------------------------------------------------------------

Pinging 176.56.238.3 with 32 bytes of data:
Reply from 176.56.238.3: bytes=32 time=38ms TTL=51
Reply from 176.56.238.3: bytes=32 time=38ms TTL=51
Reply from 176.56.238.3: bytes=32 time=38ms TTL=51
Reply from 176.56.238.3: bytes=32 time=38ms TTL=51

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

Location: Europe, Lithuania.

Pinging 95.47.119.2 with 32 bytes of data:
Reply from 95.47.119.2: bytes=32 time=45ms TTL=55
Reply from 95.47.119.2: bytes=32 time=44ms TTL=55
Reply from 95.47.119.2: bytes=32 time=44ms TTL=55
Reply from 95.47.119.2: bytes=32 time=44ms TTL=55

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

-------------------------------------------------------------------------

Pinging 176.56.238.3 with 32 bytes of data:
Reply from 176.56.238.3: bytes=32 time=38ms TTL=51
Reply from 176.56.238.3: bytes=32 time=38ms TTL=51
Reply from 176.56.238.3: bytes=32 time=38ms TTL=51
Reply from 176.56.238.3: bytes=32 time=38ms TTL=51

Ping statistics for 176.56.238.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 38ms, Average = 38ms
5
#5
1 Frags +

From Austin, TX, USA:

Pinging 95.47.119.2 with 32 bytes of data:
Reply from 95.47.119.2: bytes=32 time=180ms TTL=40
Reply from 95.47.119.2: bytes=32 time=183ms TTL=40
Reply from 95.47.119.2: bytes=32 time=182ms TTL=40
Reply from 95.47.119.2: bytes=32 time=181ms TTL=40

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

Pinging 176.56.238.3 with 32 bytes of data:
Reply from 176.56.238.3: bytes=32 time=187ms TTL=42
Reply from 176.56.238.3: bytes=32 time=187ms TTL=42
Reply from 176.56.238.3: bytes=32 time=187ms TTL=42
Reply from 176.56.238.3: bytes=32 time=188ms TTL=42

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

From Austin, TX, USA:

Pinging 95.47.119.2 with 32 bytes of data:
Reply from 95.47.119.2: bytes=32 time=180ms TTL=40
Reply from 95.47.119.2: bytes=32 time=183ms TTL=40
Reply from 95.47.119.2: bytes=32 time=182ms TTL=40
Reply from 95.47.119.2: bytes=32 time=181ms TTL=40

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


Pinging 176.56.238.3 with 32 bytes of data:
Reply from 176.56.238.3: bytes=32 time=187ms TTL=42
Reply from 176.56.238.3: bytes=32 time=187ms TTL=42
Reply from 176.56.238.3: bytes=32 time=187ms TTL=42
Reply from 176.56.238.3: bytes=32 time=188ms TTL=42

Ping statistics for 176.56.238.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 188ms, Average = 187ms
6
#6
1 Frags +

Location: South Carolina, USA

http://i.imgur.com/KaDY3UT.png

Location: South Carolina, USA

[img]http://i.imgur.com/KaDY3UT.png[/img]
7
#7
1 Frags +

Here's some tracerts too:

Tracing route to ams-nl.lg.iniz.com [95.47.119.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms E3000 [192.168.10.1]
2 8 ms 8 ms 7 ms 142.254.128.37
3 9 ms 7 ms 7 ms tge7-1.ausutxla02h.texas.rr.com [66.68.2.178]
4 21 ms 9 ms 11 ms tge0-15-0-2.ausutxla01r.texas.rr.com [24.175.42.232]
5 17 ms 21 ms 15 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 18 ms 15 ms 14 ms 107.14.17.136
7 13 ms 14 ms 17 ms 107.14.19.97
8 24 ms 36 ms 40 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97]
9 15 ms 16 ms 12 ms ae6.dal33.ip4.tinet.net [199.229.230.85]
10 125 ms 128 ms 126 ms xe-4-0-0.ams12.ip4.tinet.net [89.149.187.206]
11 171 ms 171 ms 174 ms nforce-gw.ip4.tinet.net [77.67.90.86]
12 179 ms 179 ms 179 ms 14-239-159-85.rtr1.z1a-d18.tc5.nl.nforce.com [85.159.239.14]
13 173 ms 173 ms 185 ms 26-239-159-85.rtr2.dbn.nl.nforce.com [85.159.239.26]
14 171 ms 168 ms 172 ms 209.146.201.109.rtr1.dba.nl.iniz.com [109.201.146.209]
15 178 ms 174 ms 174 ms nl-cx2.routingdns.net [95.47.141.6]
16 179 ms 179 ms 179 ms ams-nl.lg.iniz.com [95.47.119.2]

Trace complete.

Tracing route to test.nl.ramnode.com [176.56.238.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms E3000 [192.168.10.1]
2 7 ms 7 ms 9 ms 142.254.128.37
3 16 ms 7 ms 8 ms tge7-1.ausutxla02h.texas.rr.com [66.68.2.178]
4 13 ms 11 ms 10 ms tge0-15-0-0.ausutxla01r.texas.rr.com [66.68.2.23]
5 13 ms 14 ms 15 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 32 ms 14 ms 14 ms 107.14.17.136
7 22 ms 12 ms 13 ms ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
8 13 ms 68 ms 13 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97]
9 133 ms 150 ms 132 ms if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5]
10 139 ms * * if-10-3.tcore1.AEQ-Ashburn.as6453.net [66.198.154.117]
11 141 ms 164 ms * if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1]
12 165 ms 136 ms * if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.138]
13 136 ms 133 ms 138 ms if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1]
14 132 ms 131 ms 133 ms if-4-2.tcore1.L78-London.as6453.net [80.231.130.33]
15 136 ms 136 ms 148 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]
16 130 ms 131 ms 133 ms if-8-2.tcore2.AV2-Amsterdam.as6453.net [80.231.131.6]
17 130 ms 131 ms 129 ms if-13-2.tcore1.AV2-Amsterdam.as6453.net [80.231.152.21]
18 185 ms 185 ms 184 ms 195.219.194.82
19 143 ms 139 ms 165 ms jointtransit.dataplace.nl.as198203.net [217.170.23.236]
20 183 ms 180 ms 179 ms 176.56.238.2
21 187 ms 186 ms 189 ms test.nl.ramnode.com [176.56.238.3]

Trace complete.

Here's some tracerts too:

Tracing route to ams-nl.lg.iniz.com [95.47.119.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms E3000 [192.168.10.1]
2 8 ms 8 ms 7 ms 142.254.128.37
3 9 ms 7 ms 7 ms tge7-1.ausutxla02h.texas.rr.com [66.68.2.178]
4 21 ms 9 ms 11 ms tge0-15-0-2.ausutxla01r.texas.rr.com [24.175.42.232]
5 17 ms 21 ms 15 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 18 ms 15 ms 14 ms 107.14.17.136
7 13 ms 14 ms 17 ms 107.14.19.97
8 24 ms 36 ms 40 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97]
9 15 ms 16 ms 12 ms ae6.dal33.ip4.tinet.net [199.229.230.85]
10 125 ms 128 ms 126 ms xe-4-0-0.ams12.ip4.tinet.net [89.149.187.206]
11 171 ms 171 ms 174 ms nforce-gw.ip4.tinet.net [77.67.90.86]
12 179 ms 179 ms 179 ms 14-239-159-85.rtr1.z1a-d18.tc5.nl.nforce.com [85.159.239.14]
13 173 ms 173 ms 185 ms 26-239-159-85.rtr2.dbn.nl.nforce.com [85.159.239.26]
14 171 ms 168 ms 172 ms 209.146.201.109.rtr1.dba.nl.iniz.com [109.201.146.209]
15 178 ms 174 ms 174 ms nl-cx2.routingdns.net [95.47.141.6]
16 179 ms 179 ms 179 ms ams-nl.lg.iniz.com [95.47.119.2]

Trace complete.


Tracing route to test.nl.ramnode.com [176.56.238.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms E3000 [192.168.10.1]
2 7 ms 7 ms 9 ms 142.254.128.37
3 16 ms 7 ms 8 ms tge7-1.ausutxla02h.texas.rr.com [66.68.2.178]
4 13 ms 11 ms 10 ms tge0-15-0-0.ausutxla01r.texas.rr.com [66.68.2.23]
5 13 ms 14 ms 15 ms agg22.dllatxl3-cr01.texas.rr.com [24.175.41.46]
6 32 ms 14 ms 14 ms 107.14.17.136
7 22 ms 12 ms 13 ms ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
8 13 ms 68 ms 13 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97]
9 133 ms 150 ms 132 ms if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5]
10 139 ms * * if-10-3.tcore1.AEQ-Ashburn.as6453.net [66.198.154.117]
11 141 ms 164 ms * if-2-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.1]
12 165 ms 136 ms * if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.138]
13 136 ms 133 ms 138 ms if-2-2.tcore1.NJY-Newark.as6453.net [66.198.70.1]
14 132 ms 131 ms 133 ms if-4-2.tcore1.L78-London.as6453.net [80.231.130.33]
15 136 ms 136 ms 148 ms if-2-2.tcore2.L78-London.as6453.net [80.231.131.1]
16 130 ms 131 ms 133 ms if-8-2.tcore2.AV2-Amsterdam.as6453.net [80.231.131.6]
17 130 ms 131 ms 129 ms if-13-2.tcore1.AV2-Amsterdam.as6453.net [80.231.152.21]
18 185 ms 185 ms 184 ms 195.219.194.82
19 143 ms 139 ms 165 ms jointtransit.dataplace.nl.as198203.net [217.170.23.236]
20 183 ms 180 ms 179 ms 176.56.238.2
21 187 ms 186 ms 189 ms test.nl.ramnode.com [176.56.238.3]

Trace complete.
8
#8
1 Frags +

Thank you TechDude.

Thank you TechDude.
9
#9
3 Frags +

Rome, Italy

#1: 95.47.119.2 (Amsterdam, The Netherlands)

Pinging 95.47.119.2 with 32 bytes of data:
Reply from 95.47.119.2: bytes=32 time=44ms TTL=54
Reply from 95.47.119.2: bytes=32 time=44ms TTL=54
Reply from 95.47.119.2: bytes=32 time=43ms TTL=54
Reply from 95.47.119.2: bytes=32 time=46ms TTL=54

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

#2: 176.56.238.3 (Alblasserdam, The Netherlands)

Pinging 176.56.238.3 with 32 bytes of data:
Reply from 176.56.238.3: bytes=32 time=48ms TTL=56
Reply from 176.56.238.3: bytes=32 time=50ms TTL=56
Reply from 176.56.238.3: bytes=32 time=45ms TTL=56
Reply from 176.56.238.3: bytes=32 time=45ms TTL=56

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

Here's my crazy routings

#1
Tracing route to ams-nl.lg.iniz.com [95.47.119.2]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 * * 6 ms 151.7.194.72
3 * * 6 ms 151.7.8.2
4 68 ms 71 ms 6 ms 151.6.4.206
5 7 ms 7 ms 7 ms 151.6.1.214
6 44 ms 37 ms 37 ms ams-ix.rtr3.z4a-a06.tc2.nforce.nl [195.69.144.228]
7 44 ms 60 ms 43 ms 17-239-159-85.rtr1.z4a-a06.tc2.nl.nforce.com [85.159.239.17]
8 44 ms 61 ms 44 ms 30-239-159-85.rtr1.b06-s02-az16.gsa.nl.nforce.com [85.159.239.30]
9 36 ms 39 ms 36 ms 37-239-159-85.rtr2.dbn.nl.nforce.com [85.159.239.37]
10 35 ms 46 ms 35 ms 209.146.201.109.rtr1.dba.nl.iniz.com [109.201.146.209]
11 36 ms 36 ms 35 ms nl-cx2.routingdns.net [95.47.141.6]
12 44 ms 44 ms 44 ms ams-nl.lg.iniz.com [95.47.119.2]

Trace complete.

#2
Tracing route to test.nl.ramnode.com [176.56.238.3]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * 32 ms 151.7.8.10
4 11 ms 6 ms 6 ms 151.6.4.214
5 50 ms 7 ms 7 ms 151.6.1.214
6 35 ms 44 ms 34 ms telecity.openpeering.nl [195.69.145.197]
7 36 ms 35 ms 38 ms telecity2-1.nikhef.openpeering.nl [82.150.154.73]
8 49 ms 48 ms 47 ms jointtransit.dataplace.nl.as198203.net [217.170.23.236]
9 37 ms 37 ms 37 ms 176.56.238.2
10 45 ms 45 ms 45 ms test.nl.ramnode.com [176.56.238.3]

Trace complete.

Rome, Italy

[b]#1: 95.47.119.2 (Amsterdam, The Netherlands)
[/b]
Pinging 95.47.119.2 with 32 bytes of data:
Reply from 95.47.119.2: bytes=32 time=44ms TTL=54
Reply from 95.47.119.2: bytes=32 time=44ms TTL=54
Reply from 95.47.119.2: bytes=32 time=43ms TTL=54
Reply from 95.47.119.2: bytes=32 time=46ms TTL=54

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


[b]#2: 176.56.238.3 (Alblasserdam, The Netherlands)[/b]

Pinging 176.56.238.3 with 32 bytes of data:
Reply from 176.56.238.3: bytes=32 time=48ms TTL=56
Reply from 176.56.238.3: bytes=32 time=50ms TTL=56
Reply from 176.56.238.3: bytes=32 time=45ms TTL=56
Reply from 176.56.238.3: bytes=32 time=45ms TTL=56

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

Here's my crazy routings

[b]#1[/b]
Tracing route to ams-nl.lg.iniz.com [95.47.119.2]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 * * 6 ms 151.7.194.72
3 * * 6 ms 151.7.8.2
4 68 ms 71 ms 6 ms 151.6.4.206
5 7 ms 7 ms 7 ms 151.6.1.214
6 44 ms 37 ms 37 ms ams-ix.rtr3.z4a-a06.tc2.nforce.nl [195.69.144.228]
7 44 ms 60 ms 43 ms 17-239-159-85.rtr1.z4a-a06.tc2.nl.nforce.com [85.159.239.17]
8 44 ms 61 ms 44 ms 30-239-159-85.rtr1.b06-s02-az16.gsa.nl.nforce.com [85.159.239.30]
9 36 ms 39 ms 36 ms 37-239-159-85.rtr2.dbn.nl.nforce.com [85.159.239.37]
10 35 ms 46 ms 35 ms 209.146.201.109.rtr1.dba.nl.iniz.com [109.201.146.209]
11 36 ms 36 ms 35 ms nl-cx2.routingdns.net [95.47.141.6]
12 44 ms 44 ms 44 ms ams-nl.lg.iniz.com [95.47.119.2]

Trace complete.

[b]#2[/b]
Tracing route to test.nl.ramnode.com [176.56.238.3]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * 32 ms 151.7.8.10
4 11 ms 6 ms 6 ms 151.6.4.214
5 50 ms 7 ms 7 ms 151.6.1.214
6 35 ms 44 ms 34 ms telecity.openpeering.nl [195.69.145.197]
7 36 ms 35 ms 38 ms telecity2-1.nikhef.openpeering.nl [82.150.154.73]
8 49 ms 48 ms 47 ms jointtransit.dataplace.nl.as198203.net [217.170.23.236]
9 37 ms 37 ms 37 ms 176.56.238.2
10 45 ms 45 ms 45 ms test.nl.ramnode.com [176.56.238.3]

Trace complete.
10
#10
1 Frags +

Averaged 115ish from Ohio on both (USA)

Averaged 115ish from Ohio on both (USA)
11
#11
0 Frags +

Thank you!

Thank you!
12
#12
1 Frags +

(Amsterdam, The Netherlands):
Minimum = 3ms, Maximum = 4ms, Average = 3ms

(Alblasserdam, The Netherlands):
Minimum = 4ms, Maximum = 4ms, Average = 4ms

Eindhoven via Nikhef

(Amsterdam, The Netherlands):
--- 95.47.119.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8997ms
rtt min/avg/max/mdev = 98.510/106.085/124.515/8.219 ms

(Alblasserdam, The Netherlands):
--- 176.56.238.3 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9002ms
rtt min/avg/max/mdev = 101.873/102.030/102.447/0.355 ms

Illinois via atrato

[b](Amsterdam, The Netherlands):[/b]
Minimum = 3ms, Maximum = 4ms, Average = 3ms

[b](Alblasserdam, The Netherlands):[/b]
Minimum = 4ms, Maximum = 4ms, Average = 4ms

Eindhoven via Nikhef


[b](Amsterdam, The Netherlands):[/b]
--- 95.47.119.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8997ms
rtt min/avg/max/mdev = 98.510/106.085/124.515/8.219 ms

[b](Alblasserdam, The Netherlands):[/b]
--- 176.56.238.3 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9002ms
rtt min/avg/max/mdev = 101.873/102.030/102.447/0.355 ms

Illinois via atrato
Please sign in through STEAM to post a comment.