Jump to content
Welcome to the virtual battlefield, Guest!

World War II Online is a Massively Multiplayer Online First Person Shooter based in Western Europe between 1939 and 1943. Through land, sea, and air combat using a ultra-realistic game engine, combined with a strategic layer, in the largest game world ever created - We offer the best WWII simulation experience around.

Sign InNEW? GET STARTED HERE

bad ping new server

barbiere3

By barbiere3,
in GAMEPLAY SUPPORT/TRAINING

 Share

Recommended Posts

barbiere3

barbiere3

Posted
Posted

Hi Crs

Im Barbiere, from Italy

after you moved the server to the new site my latency changed slightly ... and for the worse!

before I played with an average of 150/200 ms now I go quietly on 200/250 and sometimes exceed 300ms, both with 4G connectivity and with 100Mb fiber of the company in which I work.

I did a "tracert" from home to understand why this high latency, I have these values from my company to our partner in China!

this is ip addr.  (38.100.251.144)

look route.....

Traccia instradamento verso 38.100.215.144 su un massimo di 30 punti di passaggio

  1     6 ms     2 ms     1 ms  192.168.42.129
  2    47 ms    37 ms    39 ms  10.120.0.1
  3    80 ms     *       75 ms  192.168.252.30
  4    54 ms    46 ms    54 ms  192.168.255.23
  5    42 ms    35 ms    50 ms  station9.lille.crefac.com [194.149.188.18]
  6    50 ms    44 ms    43 ms  16.187.149.194.te-dns.org [194.149.187.16]
  7    96 ms    45 ms    47 ms  ppp3-toulouse.isdnet.net [194.149.170.130]
  8    89 ms    55 ms    58 ms  ppp2-toulouse.isdnet.net [194.149.170.129]
  9   112 ms    59 ms    60 ms  p11-crs16-1-be1109.intf.routers.proxad.net [194.149.160.197]
 10   100 ms    63 ms    60 ms  194.149.166.38
 11   104 ms    65 ms    62 ms  be4204.ccr32.par04.atlas.cogentco.com [149.11.115.13]
 12   102 ms    66 ms    59 ms  be2103.ccr42.par01.atlas.cogentco.com [154.54.61.21]
 13    97 ms    72 ms    71 ms  be12489.ccr42.lon13.atlas.cogentco.com [154.54.57.69]
 14   169 ms   141 ms   131 ms  be2101.ccr32.bos01.atlas.cogentco.com [154.54.82.38]
 15   158 ms   146 ms   140 ms  be3600.ccr22.alb02.atlas.cogentco.com [154.54.0.221]
 16   171 ms   147 ms   145 ms  be2879.ccr22.cle04.atlas.cogentco.com [154.54.29.173]
 17   186 ms   160 ms   160 ms  be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
 18   177 ms   168 ms   168 ms  be2832.ccr22.mci01.atlas.cogentco.com [154.54.44.169]
 19   214 ms   190 ms   181 ms  be3036.ccr22.den01.atlas.cogentco.com [154.54.31.89]
 20   224 ms   193 ms   190 ms  be3038.ccr32.slc01.atlas.cogentco.com [154.54.42.97]
 21   243 ms   213 ms   211 ms  be2029.ccr22.sea02.atlas.cogentco.com [154.54.86.110]
 22   238 ms   213 ms   214 ms  be2670.ccr21.pdx01.atlas.cogentco.com [154.54.42.150]
 23   245 ms   217 ms   214 ms  be3658.agr11.pdx01.atlas.cogentco.com [154.54.86.226]
 24   250 ms   219 ms   215 ms  te0-0-2-3.nr11.b057349-1.pdx01.atlas.cogentco.com [154.24.51.134]
 25   235 ms   218 ms   223 ms  38.104.104.194
 26   225 ms   216 ms   215 ms  gi0-0-0-8.nr11.b057349-1.pdx01.atlas.cogentco.com [38.104.104.193]
 27     *        *        *     Richiesta scaduta.
 28     *        *        *     Richiesta scaduta.
 29     *        *        *     Richiesta scaduta.
 30     *        *        *

 


Arrival in Usa in the network of "cogentco" with a discreet ping (60/70), then it is a delusion of "hop", never seen so many rebounds and losing so many ms!
I have some doubts about the quality of this routing.

The writer is the IT infrastructure manager of a company and I hope I have helped you.

ciao!

 

 

Link to comment
Share on other sites
removed1

removed1

Posted
Posted

Hey

 

I have the same problem 

Tracing route to 38.100.251.144 over a maximum of 30 hops
  1    <1 ms    <1 ms    <1 ms  myhome.mynet [192.168.1.1]
  2     3 ms    <1 ms    <1 ms  100.96.18.1
  3     1 ms    <1 ms    <1 ms  77.68.247.51
  4     1 ms    <1 ms     2 ms  77.68.247.53
  5     1 ms    <1 ms    <1 ms  77.68.247.55
  6     *        *        *     Request timed out.
  7     5 ms     4 ms     4 ms  be201.salt-pe30.link.stofa.net [212.10.15.218]
  8     5 ms     4 ms     5 ms  be212.fjer-pe30.link.stofa.net [212.10.13.128]
  9     4 ms     4 ms     4 ms  be210.logs-pe30.link.stofa.net [212.10.13.94]
 10     4 ms     4 ms     5 ms  be208.alv-dist01.link.stofa.net [178.155.254.238]
 11     4 ms     4 ms     4 ms  be204.aarh-cor01.link.stofa.net [178.155.255.150]
 12     4 ms     4 ms     4 ms  be101.aarh-br01.link.stofa.net [212.10.45.174]
 13     4 ms     4 ms     4 ms  100.127.255.253
 14     5 ms     4 ms     4 ms  be12-4094.aarh-br01.link.stofa.net [212.10.25.102]
 15     9 ms     7 ms     7 ms  be102.aarh-cor02.link.stofa.net [212.10.45.177]
 16     8 ms     7 ms     7 ms  be191.aarh-cor03.link.stofa.net [178.155.255.254]
 17     7 ms     7 ms     7 ms  be183.hrsk-cor03.link.stofa.net [89.184.128.175]
 18     7 ms     7 ms     7 ms  be101.hrsk-br01.link.stofa.net [212.10.45.194]
 19     7 ms     7 ms     7 ms  212.73.252.65
 20     7 ms     7 ms     7 ms  ae-1-11.bar1.Copenhagen1.Level3.net [4.69.210.210]
 21     7 ms     7 ms     7 ms  ae-1-11.bar1.Copenhagen1.Level3.net [4.69.210.210]
 22     7 ms     8 ms     7 ms  Cogent-level3-40G.Copenhagen1.Level3.net [4.68.75.86]
 23    18 ms    18 ms    19 ms  be2303.ccr41.ham01.atlas.cogentco.com [130.117.3.161]
 24    20 ms    18 ms    18 ms  be2815.ccr41.ams03.atlas.cogentco.com [154.54.38.205]
 25    93 ms    93 ms    93 ms  be12194.ccr41.lon13.atlas.cogentco.com [154.54.56.93]
 26    93 ms    93 ms    94 ms  be2317.ccr41.jfk02.atlas.cogentco.com [154.54.30.185]
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
Trace complete.
 
Her is ping at first connection
Pinging 130.117.3.161 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 4.68.75.86: Destination net unreachable.
Reply from 4.68.75.86: Destination net unreachable.
Ping statistics for 130.117.3.161:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
 
Her is the second
C:\Users\johnn>ping 154.54.38.205
Pinging 154.54.38.205 with 32 bytes of data:
Reply from 154.54.38.205: bytes=32 time=18ms TTL=238
Reply from 154.54.38.205: bytes=32 time=18ms TTL=238
Reply from 154.54.38.205: bytes=32 time=18ms TTL=238
Reply from 154.54.38.205: bytes=32 time=18ms TTL=238
Ping statistics for 154.54.38.205:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 18ms, Average = 18ms
 
Here is the thridr
C:\Users\johnn>ping 154.54.56.93
Pinging 154.54.56.93 with 32 bytes of data:
Reply from 154.54.56.93: bytes=32 time=27ms TTL=235
Reply from 154.54.56.93: bytes=32 time=27ms TTL=235
Reply from 154.54.56.93: bytes=32 time=27ms TTL=235
Reply from 154.54.56.93: bytes=32 time=26ms TTL=235
Ping statistics for 154.54.56.93:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 26ms, Maximum = 27ms, Average = 26ms
 
Here is the 4
C:\Users\johnn>ping 154.54.30.185
Pinging 154.54.30.185 with 32 bytes of data:
Reply from 154.54.30.185: bytes=32 time=95ms TTL=233
Reply from 154.54.30.185: bytes=32 time=95ms TTL=233
Reply from 154.54.30.185: bytes=32 time=95ms TTL=233
Reply from 154.54.30.185: bytes=32 time=95ms TTL=233
Ping statistics for 154.54.30.185:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 95ms, Maximum = 95ms, Average = 95ms
 
 
When you get this ham01.atlas.cogentco.com [130.117.3.161] this is the main problem for it is going to loop and make packet collesions 
You shall look at 130.117.3.161 for it is making problems in routing to the other IP adresses it looks like it is bouncing 
Link to comment
Share on other sites
Kilemall

Kilemall

Posted
Posted

One of the negatives of a cheaper siting is likely being more 'off the beaten path', for an international FPS game may hurt more distant players.

Hopefully this is a true hardware/local LAN upgrade and better timers between game services internally can help offset some of this.

  • Like 1
Link to comment
Share on other sites
base21

base21

Posted
Posted

The routing to end connection is subject to be set by your local ISP?

Is this true?

good thing to know as I will be changing ISP for a new location.

Link to comment
Share on other sites
barbiere

barbiere

Posted
Posted

@CHOAD: ok my example was from 4g connection of my home, now i report tracert from 100Mb fiber from my  company.

Traccia instradamento verso 38.100.251.144 su un massimo di 30 punti di passaggio

  1     1 ms     1 ms     1 ms      :)
  2     2 ms     2 ms     2 ms      :)
  3    10 ms    12 ms    12 ms  h213-213-127-85.albacom.net [213.213.127.85]
  4    10 ms    10 ms    10 ms  213.213.61.76
  5    10 ms    10 ms    10 ms  mno-b2-link.telia.net [80.239.128.229]
  6    17 ms    17 ms    17 ms  mei-b1-link.telia.net [62.115.112.247]
  7    16 ms    17 ms    32 ms  mei-b2-link.telia.net [62.115.116.26]
  8    16 ms    16 ms    16 ms  mei-b3-link.telia.net [62.115.116.12]
  9    38 ms    39 ms    29 ms  cogent-ic-344184-mei-b3.c.telia.net [62.115.179.97]
 10    17 ms    17 ms    17 ms  be2345.ccr21.mrs01.atlas.cogentco.com [154.54.38.169]
 11    34 ms    29 ms    28 ms  be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
 12   112 ms   112 ms   112 ms  be3627.ccr41.jfk02.atlas.cogentco.com [66.28.4.197]
 13     *        *        *     Richiesta scaduta.
 14     *        *        *     Richiesta scaduta.
 15     *        *        *     Richiesta scaduta.
 16     *        *        *     Richiesta scaduta.
 17     *        *        *     Richiesta scaduta.
 18     *        *        *     Richiesta scaduta.
 19     *        *        *     Richiesta scaduta.
 20     *        *        *     Richiesta scaduta.
 21     *        *        *     Richiesta scaduta.
 22     *        *        *     Richiesta scaduta.
 23     *        *        *     Richiesta scaduta.
 24     *        *        *     Richiesta scaduta.

.................

When i arrived in cogentco network, after pair of hop, the connection worsens .

 

@BASE21 :  yes, only for enterprise connection; for example if you want to give a good web service for the world it is advisable to look for an isp that has good pops

 

Link to comment
Share on other sites
MikeAZ

MikeAZ

Posted
Posted
On 12/30/2019 at 1:25 AM, barbiere3 said:

Hi Crs

Im Barbiere, from Italy

after you moved the server to the new site my latency changed slightly ... and for the worse!

before I played with an average of 150/200 ms now I go quietly on 200/250 and sometimes exceed 300ms, both with 4G connectivity and with 100Mb fiber of the company in which I work.

I did a "tracert" from home to understand why this high latency, I have these values from my company to our partner in China!

this is ip addr.  (38.100.251.144)

look route.....

Traccia instradamento verso 38.100.215.144 su un massimo di 30 punti di passaggio

  1     6 ms     2 ms     1 ms  192.168.42.129
  2    47 ms    37 ms    39 ms  10.120.0.1
  3    80 ms     *       75 ms  192.168.252.30
  4    54 ms    46 ms    54 ms  192.168.255.23
  5    42 ms    35 ms    50 ms  station9.lille.crefac.com [194.149.188.18]
  6    50 ms    44 ms    43 ms  16.187.149.194.te-dns.org [194.149.187.16]
  7    96 ms    45 ms    47 ms  ppp3-toulouse.isdnet.net [194.149.170.130]
  8    89 ms    55 ms    58 ms  ppp2-toulouse.isdnet.net [194.149.170.129]
  9   112 ms    59 ms    60 ms  p11-crs16-1-be1109.intf.routers.proxad.net [194.149.160.197]
 10   100 ms    63 ms    60 ms  194.149.166.38
 11   104 ms    65 ms    62 ms  be4204.ccr32.par04.atlas.cogentco.com [149.11.115.13]
 12   102 ms    66 ms    59 ms  be2103.ccr42.par01.atlas.cogentco.com [154.54.61.21]
 13    97 ms    72 ms    71 ms  be12489.ccr42.lon13.atlas.cogentco.com [154.54.57.69]
 14   169 ms   141 ms   131 ms  be2101.ccr32.bos01.atlas.cogentco.com [154.54.82.38]
 15   158 ms   146 ms   140 ms  be3600.ccr22.alb02.atlas.cogentco.com [154.54.0.221]
 16   171 ms   147 ms   145 ms  be2879.ccr22.cle04.atlas.cogentco.com [154.54.29.173]
 17   186 ms   160 ms   160 ms  be2718.ccr42.ord01.atlas.cogentco.com [154.54.7.129]
 18   177 ms   168 ms   168 ms  be2832.ccr22.mci01.atlas.cogentco.com [154.54.44.169]
 19   214 ms   190 ms   181 ms  be3036.ccr22.den01.atlas.cogentco.com [154.54.31.89]
 20   224 ms   193 ms   190 ms  be3038.ccr32.slc01.atlas.cogentco.com [154.54.42.97]
 21   243 ms   213 ms   211 ms  be2029.ccr22.sea02.atlas.cogentco.com [154.54.86.110]
 22   238 ms   213 ms   214 ms  be2670.ccr21.pdx01.atlas.cogentco.com [154.54.42.150]
 23   245 ms   217 ms   214 ms  be3658.agr11.pdx01.atlas.cogentco.com [154.54.86.226]
 24   250 ms   219 ms   215 ms  te0-0-2-3.nr11.b057349-1.pdx01.atlas.cogentco.com [154.24.51.134]
 25   235 ms   218 ms   223 ms  38.104.104.194
 26   225 ms   216 ms   215 ms  gi0-0-0-8.nr11.b057349-1.pdx01.atlas.cogentco.com [38.104.104.193]
 27     *        *        *     Richiesta scaduta.
 28     *        *        *     Richiesta scaduta.
 29     *        *        *     Richiesta scaduta.
 30     *        *        *

 


Arrival in Usa in the network of "cogentco" with a discreet ping (60/70), then it is a delusion of "hop", never seen so many rebounds and losing so many ms!
I have some doubts about the quality of this routing.

The writer is the IT infrastructure manager of a company and I hope I have helped you.

ciao!

 

 

what is this witchcraft?

Link to comment
Share on other sites
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...