Cannot update and lose connection every few minutes

[Naarkie]

Code: Select all

Pinging faforever.com [91.236.254.74] with 32 bytes of data:
Reply from 91.236.254.74: bytes=32 time=248ms TTL=49
Request timed out.
Reply from 91.236.254.74: bytes=32 time=372ms TTL=49
Reply from 91.236.254.74: bytes=32 time=257ms TTL=49
Request timed out.
Reply from 91.236.254.74: bytes=32 time=254ms TTL=49
Reply from 91.236.254.74: bytes=32 time=355ms TTL=49
Request timed out.
Reply from 91.236.254.74: bytes=32 time=222ms TTL=49
Reply from 91.236.254.74: bytes=32 time=304ms TTL=49
Reply from 91.236.254.74: bytes=32 time=361ms TTL=49
Reply from 91.236.254.74: bytes=32 time=203ms TTL=49
Reply from 91.236.254.74: bytes=32 time=342ms TTL=49
Reply from 91.236.254.74: bytes=32 time=219ms TTL=49
Reply from 91.236.254.74: bytes=32 time=235ms TTL=49
Reply from 91.236.254.74: bytes=32 time=298ms TTL=49
Reply from 91.236.254.74: bytes=32 time=289ms TTL=49
Reply from 91.236.254.74: bytes=32 time=464ms TTL=49
Reply from 91.236.254.74: bytes=32 time=311ms TTL=49
Reply from 91.236.254.74: bytes=32 time=262ms TTL=49
Reply from 91.236.254.74: bytes=32 time=294ms TTL=49
Reply from 91.236.254.74: bytes=32 time=253ms TTL=49
Reply from 91.236.254.74: bytes=32 time=277ms TTL=49
Reply from 91.236.254.74: bytes=32 time=299ms TTL=49
Request timed out.
Reply from 91.236.254.74: bytes=32 time=310ms TTL=49
Reply from 91.236.254.74: bytes=32 time=321ms TTL=49
Reply from 91.236.254.74: bytes=32 time=285ms TTL=49
Reply from 91.236.254.74: bytes=32 time=291ms TTL=49
Reply from 91.236.254.74: bytes=32 time=286ms TTL=49
Reply from 91.236.254.74: bytes=32 time=300ms TTL=49
Request timed out.
Reply from 91.236.254.74: bytes=32 time=308ms TTL=49
Reply from 91.236.254.74: bytes=32 time=232ms TTL=49
Reply from 91.236.254.74: bytes=32 time=221ms TTL=49
Reply from 91.236.254.74: bytes=32 time=373ms TTL=49
Reply from 91.236.254.74: bytes=32 time=214ms TTL=49
Reply from 91.236.254.74: bytes=32 time=291ms TTL=49
Reply from 91.236.254.74: bytes=32 time=278ms TTL=49
Reply from 91.236.254.74: bytes=32 time=277ms TTL=49
Request timed out.
Reply from 91.236.254.74: bytes=32 time=271ms TTL=49
Reply from 91.236.254.74: bytes=32 time=271ms TTL=49
Reply from 91.236.254.74: bytes=32 time=498ms TTL=49
Request timed out.
Reply from 91.236.254.74: bytes=32 time=365ms TTL=49
Reply from 91.236.254.74: bytes=32 time=306ms TTL=49
Reply from 91.236.254.74: bytes=32 time=272ms TTL=49
Reply from 91.236.254.74: bytes=32 time=281ms TTL=49
Reply from 91.236.254.74: bytes=32 time=266ms TTL=49
Reply from 91.236.254.74: bytes=32 time=317ms TTL=49
Reply from 91.236.254.74: bytes=32 time=258ms TTL=49
Reply from 91.236.254.74: bytes=32 time=359ms TTL=49
Reply from 91.236.254.74: bytes=32 time=214ms TTL=49
Reply from 91.236.254.74: bytes=32 time=211ms TTL=49
Reply from 91.236.254.74: bytes=32 time=441ms TTL=49
Reply from 91.236.254.74: bytes=32 time=311ms TTL=49
Reply from 91.236.254.74: bytes=32 time=203ms TTL=49
Reply from 91.236.254.74: bytes=32 time=239ms TTL=49
Reply from 91.236.254.74: bytes=32 time=342ms TTL=49
Reply from 91.236.254.74: bytes=32 time=274ms TTL=49
Reply from 91.236.254.74: bytes=32 time=336ms TTL=49
Reply from 91.236.254.74: bytes=32 time=222ms TTL=49
Reply from 91.236.254.74: bytes=32 time=315ms TTL=49
Reply from 91.236.254.74: bytes=32 time=361ms TTL=49
Reply from 91.236.254.74: bytes=32 time=247ms TTL=49
Reply from 91.236.254.74: bytes=32 time=559ms TTL=49
Reply from 91.236.254.74: bytes=32 time=249ms TTL=49
Reply from 91.236.254.74: bytes=32 time=264ms TTL=49
Reply from 91.236.254.74: bytes=32 time=373ms TTL=49
Reply from 91.236.254.74: bytes=32 time=203ms TTL=49
Request timed out.
Reply from 91.236.254.74: bytes=32 time=276ms TTL=49

Ping statistics for 91.236.254.74:
    Packets: Sent = 73, Received = 65, Lost = 8 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 203ms, Maximum = 559ms, Average = 295ms
Control-C
^C


Nothing abnormal really.

[Ze_PilOt]

You have a lot of request time out. It's really not normal.
10% Packet loss is HUGE actually.

Also, the ping time is really huge too. It's around 24ms in most of europe.

Ping to faforever.com from around the world :

ping.jpg (272.96 KiB) Viewed 1228 times

For the ping time and packet loss, it seems that you connect from china.



Can you post the result of "tracert faforever.com" ?

[Naarkie]

Connecting from South Africa actually, 250ms delay to Europe is normal.

Code: Select all


Tracing route to faforever.com [91.236.254.74]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    91 ms   149 ms   112 ms  41-132-26-1.dsl.mweb.co.za [41.132.26.1]
  3   122 ms    85 ms   127 ms  197-80-4-210.jhb.mweb.co.za [197.80.4.210]
  4     *      274 ms     *     vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5     *      351 ms   255 ms  tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.
226]
  6   330 ms   209 ms     *     pos0-3-0-0.lon-up-1.mweb.co.za [197.80.5.9]
  7   279 ms   344 ms   330 ms  176.67.177.131
  8   318 ms   239 ms   338 ms  te1-4.ccr01.lon09.atlas.cogentco.com [149.6.98.5
]
  9   313 ms     *      388 ms  te0-3-0-3.ccr21.lon01.atlas.cogentco.com [154.54
.36.165]
10   254 ms     *      320 ms  te0-5-0-6.ccr21.lon13.atlas.cogentco.com [154.54
.74.46]
11   363 ms   278 ms   326 ms  te2-1.ccr01.lil01.atlas.cogentco.com [154.54.36.
234]
12   405 ms     *      268 ms  cogent-core01.as35625.net [149.6.161.114]
13   313 ms   265 ms   253 ms  core03.as35625.net [46.29.120.19]
14   212 ms   308 ms     *     routeur-core01-1G.firstheberg.net [46.29.121.69]

15   203 ms   281 ms   278 ms  91.236.254.74

Trace complete.


[Ze_PilOt]

The ping is probably normal, but the packet loss is your problem.

I will try to improve the http download from the lobby in a next version.