Network Performance Update for DTAG Customers

Level3

Remember what you did to set up the signature? Do it again - it changes it. Wonderful.

Munich here. A couple of days ago, my prime time latency jumped from 49ms to roughly 300ms and has been deteriorating since. Yesterday it was 500ms with spikes to 9000ms.
Might that be connected to the routing changes? Because if so, I'd like to know when the trial is going to run out.


I get confused however, when comparing the tracert to Cobalt:

Routenverfolgung zu amspsn-liv-gw02.planetside2.com [69.174.194.166] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 10 ms 10 ms 10 ms 217.0.117.188
3 13 ms 11 ms 11 ms 87.186.197.226
4 15 ms 15 ms 15 ms 217.239.52.126
5 22 ms 22 ms 22 ms 62.157.250.74
6 55 ms 54 ms 55 ms ae-128-3514.edge6.Amsterdam1.Level3.net [4.69.162.230]
7 * * * Zeitüberschreitung der Anforderung.
8 * * * Zeitüberschreitung der Anforderung.
9 * * * Zeitüberschreitung der Anforderung.
10 * * * Zeitüberschreitung der Anforderung.
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.
16 * * * Zeitüberschreitung der Anforderung.
17 * * * Zeitüberschreitung der Anforderung.
18 * * * Zeitüberschreitung der Anforderung.
19 * * * Zeitüberschreitung der Anforderung.
20 * * * Zeitüberschreitung der Anforderung.
21 * * * Zeitüberschreitung der Anforderung.
22 * * * Zeitüberschreitung der Anforderung.
23 * * * Zeitüberschreitung der Anforderung.
24 * * * Zeitüberschreitung der Anforderung.
25 * * * Zeitüberschreitung der Anforderung.
26 * * * Zeitüberschreitung der Anforderung.
27 * * * Zeitüberschreitung der Anforderung.
28 * * * Zeitüberschreitung der Anforderung.
29 * * * Zeitüberschreitung der Anforderung.
30 * * * Zeitüberschreitung der Anforderung.


to a tracert to a randomly picked Teamspeak server in Amsterdam:

Routenverfolgung zu 173.199.64.244.choopa.net [173.199.64.244] über maximal 30 A
bschnitte:

1 <1 ms <1 ms <1 ms speedport.ip [192.168.2.1]
2 10 ms 10 ms 10 ms 217.0.117.188
3 14 ms 11 ms 11 ms 87.186.197.230
4 16 ms 16 ms 16 ms 217.239.52.74
5 38 ms 81 ms 41 ms te-3-0-0.edge5.Frankfurt1.Level3.net [4.68.62.141]
6 31 ms 31 ms 36 ms ae-121-3507.edge4.Amsterdam1.Level3.net [4.69.162.185]
7 25 ms 24 ms 26 ms CHOOPA-LLC.edge4.Amsterdam1.Level3.net [212.72.43.162]
8 24 ms 24 ms 24 ms 173.199.64.244.choopa.net [173.199.64.244]


Why do I have a good connection to other random servers in the Netherlands, but Cobalt seems to be located in North Korea? I mean I have roughly 1 second input lag to Jaegar or PTS, when using terminals or entering vehicles. But there are barely any problems with hit detection or people jittering and teleporting around all the time.
While Cobalt is barely playable while sober. Tanks fly around the map, enemies don't take damage at all or at the very least, hitmarkers will be delayed by 10 seconds and everybody is jittering. An effect I previously only knew from long range sniping.

Dear Devs, dear PromptCritical,

may I ask for a bit of transparency on the matter, or is this just another case of let's-ignore-the-fact-of-our-management-announcing-a-high-level-of-transparency-in-the-future?

BTW, I'm still a paying customer, who atm hasn't gotten his monthly DBC so far.

You know, at least with a bit more information on the matter maybe we stupid german fvcks might have the possibility to work with the service department of our ISP to fix or at least better the situation at hand.

Any updates on this matter? My current ping on Cobalt and Miller is constantly jumping from 120-260ms, making the game barely playable. It's now nearby a month since the last announcement and another 6 months since the first mentioning of negotiations. A little bit more communication would be really great.

its unplayable in the evening ping 400 iam located around bonn germany