*** Latency issues (Ping > 200 must read)*** - maka - 08-23-2008
Lady Minax Wrote:Pinging games05.xs4all.nl [194.109.69.205] with 32 bytes of data:
Reply from 194.109.69.205: bytes=32 time=394ms TTL=111
Reply from 194.109.69.205: bytes=32 time=394ms TTL=111
Reply from 194.109.69.205: bytes=32 time=393ms TTL=111
Reply from 194.109.69.205: bytes=32 time=393ms TTL=111
Ping statistics for 194.109.69.205:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 393ms, Maximum = 394ms, Average = 393ms
My ping on a good day.
This, sadly, is a know and unfixable issue (from our side).
*** Latency issues (Ping > 200 must read)*** -
imported_Yankovic - 08-23-2008
maka Wrote:This, sadly, is a know and unfixable issue (from our side).
It's not fixable on any side (unless you are on dialup), you just live very far from the server.
*** Latency issues (Ping > 200 must read)*** - maka - 08-24-2008
Yankovic Wrote:It's not fixable on any side (unless you are on dialup), you just live very far from the server.
It's fixable with new huge fiber under the sea, that's why i chose those words
*** Latency issues (Ping > 200 must read)*** -
imported_Yankovic - 08-24-2008
maka Wrote:It's fixable with new huge fiber under the sea, that's why i chose those words
There is actually huge fiber under the sea. All internet communications between europe and North America goes through fiber:
http://en.wikipedia.org/wiki/Transatlantic_telephone_cable
*** Latency issues (Ping > 200 must read)*** -
imported_Apollo - 08-25-2008
Yankovic Wrote:There is actually huge fiber under the sea. All internet communications between europe and North America goes through fiber: http://en.wikipedia.org/wiki/Transatlantic_telephone_cable
yup.. they are in the process of laying a new one from Australia to somewhere else... i think it goes to hawaii.... :eek:
*** Latency issues (Ping > 200 must read)*** -
imported_Fury - 02-22-2009
Tracing route to games05.xs4all.nl [194.109.69.205]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 146 ms 99 ms 44 ms bas1-quebec03_lo_SYMP.net.bell.ca [64.230.200.4]
3 289 ms 292 ms 250 ms dis10-quebec14_GE2-0-8_150.net.bell.ca [64.230.1
43.177]
4 42 ms 40 ms 55 ms core4-quebec14_POS2-0-0.net.bell.ca [64.230.170.
73]
5 44 ms 47 ms 96 ms Ncore4-montrealak_POS0-0-0-0.net.bell.ca [64.230
.147.145]
6 96 ms 123 ms 62 ms core4-montrealak_POS6-0-0_core.net.bell.ca [64.2
30.168.242]
7 212 ms 76 ms 72 ms core2-newyork83_pos_4_0_0.net.bell.ca [64.230.20
7.146]
8 97 ms 90 ms 54 ms BX5-NEWYORK83_POS12-0-0_core.net.bell.ca [64.230
.187.93]
9 202 ms 257 ms 208 ms Tenge1-2-1000M.ar5.NYC1.gblx.net [64.215.195.65]
10 273 ms 253 ms 164 ms XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.17
8]
11 189 ms 247 ms 132 ms 0.so-1-0-0.xr4.1d12.xs4all.net [194.109.5.1]
12 183 ms 132 ms 137 ms te5-4.swcolo2.1d12.xs4all.net [194.109.12.6]
13 232 ms 186 ms 206 ms games05.xs4all.nl [194.109.69.205]
Trace complete.
*** Latency issues (Ping > 200 must read)*** -
imported_Fury - 02-22-2009
Pinging games05.xs4all.nl [194.109.69.205] with 32 bytes of data:
Reply from 194.109.69.205: bytes=32 time=227ms TTL=113
Reply from 194.109.69.205: bytes=32 time=259ms TTL=113
Reply from 194.109.69.205: bytes=32 time=371ms TTL=113
Reply from 194.109.69.205: bytes=32 time=143ms TTL=113
Ping statistics for 194.109.69.205:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 143ms, Maximum = 371ms, Average = 250ms
*** Latency issues (Ping > 200 must read)*** -
imported_Fury - 02-22-2009
Pinging games05.xs4all.nl [194.109.69.205] with 32 bytes of data:
Reply from 194.109.69.205: bytes=32 time=132ms TTL=113
Reply from 194.109.69.205: bytes=32 time=259ms TTL=113
Reply from 194.109.69.205: bytes=32 time=351ms TTL=113
Reply from 194.109.69.205: bytes=32 time=302ms TTL=113
Ping statistics for 194.109.69.205:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 132ms, Maximum = 351ms, Average = 261ms