Intermittent Lag on C2Play Servers only

[Clive St Helmet]

This is a routing issue with the router at cdn77.cr1.synlinq.de.

I was incorrectly told that the issue was my ISP, which was BT. I've now moved over to Sky, so I'm with a completely different ISP, but I still have the same issue.https://drive.google.com/file/d/1uzolgb ... sp=sharing

It's definitely this router causing the issue. It is the same router as last time when I was routed through it from BT. When I contacted BT they advised me that they would not be able to contact the owner of this router, and advised me to go through you guys.

It's clearly a routing issue that affects traffic coming from the UK. The router is cdn77.cr1.synlinq.de. I don't know how much more specific I can be really.

[Edgar]

Thank you for your analysis. Coincidentally that was exactly what we have discovered yesterday in an analysis. We reported that now to CDN77 and hope that they will resolve that. If not, we need to think about an alternative solution.

[Clive St Helmet]

Thanks. For what it's worth, I've just gone away and made another demo. The problem is intermittent, but I've captured it within the last couple of minutes:

https://drive.google.com/file/d/1ug_hrN ... sp=sharing

[crash]

Good work Clive,

I am still experiencing issues and it's intermittent.

It seems like late evenings, especially around 12am or running up to that time I experience it worse.

I am on BT from the UK and hard-wired into the router, spoke to BT and cleared my line from noise and still, the issue persists intermittently.

Thanks

[Edgar]

We will change the routing in a few days for all servers, it will be very interesting if the issue then disappears.

[crash]

Thats great news!

Thank you

[crash]

This was earlier:

Tracing route to dust2.c2play.de [185.236.8.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms <1 ms <1 ms BTHUB [192.168.1.254]
3 4 ms 3 ms 4 ms 172.16.10.235
4 * * * Request timed out.
5 5 ms 5 ms 4 ms 31.55.185.184
6 5 ms 4 ms 5 ms core2-hu0-6-0-8.colindale.ukcore.bt.net [213.121.192.28]
7 5 ms 5 ms 4 ms peer7-et-4-0-4.telehouse.ukcore.bt.net [194.72.16.128]
8 5 ms 5 ms 5 ms 166-49-214-194.gia.bt.net [166.49.214.194]
9 * * * Request timed out.
10 6 ms 5 ms 5 ms be2869.ccr42.lon13.atlas.cogentco.com [154.54.57.161]
11 20 ms 22 ms 21 ms be12488.ccr42.ams03.atlas.cogentco.com [130.117.51.42]
12 21 ms 21 ms 21 ms be2814.ccr42.fra03.atlas.cogentco.com [130.117.0.142]
13 18 ms 18 ms 18 ms datacamp.demarc.cogentco.com [149.6.43.114]
14 18 ms 18 ms 18 ms unn-84-17-33-61.cdn77.com [84.17.33.61]
15 20 ms 20 ms 21 ms 45.135.200.119
16 18 ms 18 ms 18 ms ae0.11.cr3.synlinq.de [45.135.200.18]
17 17 ms 17 ms 19 ms cr1.phpfriends.de [45.135.203.115]
18 17 ms 17 ms 17 ms 185.236.8.5

This is now: 11:30pm onwards

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * 1 ms 1 ms BTHUB [192.168.1.254]
3 14 ms 3 ms 3 ms 172.16.10.235
4 * * * Request timed out.
5 5 ms 5 ms 5 ms 31.55.185.184
6 4 ms 5 ms 4 ms core2-hu0-6-0-8.colindale.ukcore.bt.net [213.121.192.28]
7 6 ms 5 ms 8 ms peer7-et-4-0-4.telehouse.ukcore.bt.net [194.72.16.128]
8 5 ms 5 ms 4 ms 166-49-214-194.gia.bt.net [166.49.214.194]
9 * * * Request timed out.
10 6 ms 5 ms 5 ms be2869.ccr42.lon13.atlas.cogentco.com [154.54.57.161]
11 20 ms 20 ms 20 ms be12488.ccr42.ams03.atlas.cogentco.com [130.117.51.42]
12 119 ms 74 ms 43 ms be2814.ccr42.fra03.atlas.cogentco.com [130.117.0.142]
13 18 ms 17 ms 17 ms datacamp.demarc.cogentco.com [149.6.43.114]
14 * 18 ms * unn-84-17-33-61.cdn77.com [84.17.33.61]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * 17 ms 185.236.8.5

[Edgar]

Has anything changed between these tracerts?

[crash]

Yes!

First one was normal , second one times out from :

14 * 18 ms * unn-84-17-33-61.cdn77.com [84.17.33.61]

I believe it was the same cdn77 that was called out previously?

[Edgar]

That was a different peer. But the timeout should not be the problem, as long there is no loss at the end target. Sometimes the peers don't answer the ICMP requests but that doesn't necessarily mean that they are offline or overloaded.

[crash]

well the second tracert was when I was having same issues as Clive

[Edgar]

@Clive St Helmet:

I added you in steam. We will probably need to do a MTR at the same time. Please let me know once you are available