My ping :(

[Aardappel]

bump for visibility, Meli and I seem to have the same problem as HotChip since a few hours... only on beginners 2

[Aardappel]

Issue seems to have resolved itself during the night.

 

things I have tried yesterday that didn’t work;

reset modem

enable DMZ in modem for my pc

reflush DNS

custom DNS (google public)

port forwarding in modem for ET

punch my monitor

Give up and watch Final Destination 2

[Aardappel]

In a crowdless server <10 human players ping was okay, but now with 20 players it got high again...

 

if anyone has a brainwave, please let me know.

 

The problem:

 

The error is only with our (Northern France) beginners 2 server (silent mod).

Normally my ping is 0 or 1.

This only affects Dutch KPN (biggest ISP of the nation) users

if I ping the ip adress of the server in windows command prompt, the response time is low.

My ping with 20 people is 130

My ping yesterday with 45 people was 400-500

[Lt Steiner]

If it is restricted only to one specific ISP, I would suspect a routing issue. If you are curious, you can do some traceroutes or pathpings to BEG 2 and find out at what specific hop the latency spikes.

 

Usually these routing issues get fixed by ISPs rather quickly. If not, you will have to contact them and notify them of the issue.

[DynaSpan]

I'm having the same issues as Meli & Aardappel, KPN network in the Netherlands. UDP traceroute on my pfSense box gives me:

 

 1  192.168.2.254  0.639 ms  0.475 ms *
 2  195.190.228.118  2.465 ms  2.163 ms  2.107 ms
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  213.251.128.66  289.013 ms
    213.186.32.210  12.923 ms  12.629 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *

 

So it looks like the hop to 213.251.128.66 is the problem. Normally I have a in-game ping of 1-10ms, now it's hovering around 400-500ms.

[Aardappel]

My tracrt
 

Tracing route to ns3050075.ip-164-132-203.eu [164.132.203.173]
over a maximum of 30 hops:

  1    <1 ms    <1 ms     1 ms  192.168.2.254
  2     3 ms     2 ms     2 ms  static.kpn.net [195.190.228.110]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8   502 ms   468 ms   598 ms  be104.gra-g2-nc5.fr.eu [213.251.128.66]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    14 ms    12 ms    13 ms  ns3050075.ip-164-132-203.eu [164.132.203.173]

 

[DynaSpan]

Seems fixed now for me, Aardappel & Meli, for some reason. Probably the route got resolved more efficiently automatically.

[Aardappel]

I did a ping to 213.251.128.66 and suddenly it all worked again. Let's hope it stays like this for now

 

Welcome to the forums Mili!

[Lt Steiner]

Hop 8 it was, probably sitting right at the transition from the Netherlands to France. Often times issues such as these occur during and due to maintenance work, and therefore are only temporary.