Ok, we finished some additional adjustments to our CDN and at least for us the speed has improved.
Could you please give us some feedback how it looks on your end?
what about the dutch servers who are in or going into the endgame?
All other servers are affected, so those you mentioned included.
We are seeing reports from some players that it works better now and from some that the performance went down.
For us it's a rollercoaster as well, so we are not quite done yet with this.
This problem we are fixing does not apply to the PX servers or the DE servers (except the DE18).
Hopefully we'll be able to fix the issue before the weekend on all affected servers.
We are still working on the matter. Even after switching the CDN we are still encountering long loading times in certain areas of the game.
We will keep you posted of course.
Thank you both for the confirmation. It fits with what we are seeing in the logs and our own tests.
If everything goes according to plan, all affected servers will be fixed sometime this afternoon.
We just implemented a workaround (as a test) on COM2, COM5, COM101 and COM201.
A complete relog is needed for the fix to take effect. Could you please give us feedback if the loading times are now better / back to normal?
Edit: According to our observations the fix is working and we have thus increased the pool of servers that have received the update now.
The following servers also received the update:
com1 com3 com202 com203 fr1 fr3 fr101 fr201 fr202 m1 m1101 m1201 gr1 es1 es2 es201 pt1 pt2 ru1 ru2 ru3 ru5 ru6 ru7 ru8 ru15 ru101 ru103 ru105 ru201 ru203 ru204
Before we update the remaining servers we want to make sure that the added traffic to our new CDN doesn't cause ans unforseen issues.
is there any kind of information we as players can provide to you to find or rule out issues?
Thanks for the offer. We already ruled out everything that is player-related.
The fault lies clearly at the the side of one of our server providers and they are trying to figure out why this changed all of a sudden.
But we are working on an alternative / workaround where we are not reliant on the affected sub-system.
Stop putting band-aids on the issues and actually fix the problems. Best example would be the fact that chat doesn’t work in the game. This has been an issue in the game for nearly 8 years. Nothing’s been done about it yet.
That is "an" issue, but not the topic of this thread.
We are discussing here a very specific technical issue, not a bug in the game. And without knowning the cause, we cannot fix it. So I fear there is no way around an investigation.
We are still investigating the issue with our provider and looking into alternatives to fix the issue.
I have forwarded your feedback to them and hopefully it will help them find the cause of the issue.
I am happy to hear that, I will forward that feedback.
How about for the others? Is the performance back to normal?
However, we haven't gotten the all clear from our provider yet, so they are still working on the issue.
For us the situation got better but there are still some areas in the game that are loading a bit sluggish.
Thanks everyone - you can stop sending us your traceroutes.
We ruled out the routing theory, everything looks good in that regard.
We are looking into some other possible causes with our provider. Unfortunately I cannot provide you with an ETA at this point.
Yes, I'm having the same problem from UK on server Loch Ness com202. Unplayable at times with a lag of 10s+ for each mouse click.
Tracing route to com202.railnation-game.com [22.214.171.124]
over a maximum of 30 hops:
1 10 ms <1 ms <1 ms Orac-Station-XI [172.30.30.1]
2 2 ms 2 ms 2 ms 172.16.15.67
3 * * * Request timed out.
4 7 ms 13 ms 7 ms 126.96.36.199
5 23 ms 59 ms 34 ms peer2-et3-0-6.slough.ukcore.bt.net [188.8.131.52]
6 8 ms 8 ms 8 ms 184.108.40.206
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 21 ms 20 ms 20 ms 220.127.116.11
Thanks for the info. Your trace is absolutely fine.
Which confirms what our own tests show.
We are looking into other possible causes atm with our server provider.
Ok, no worries.
We are investigating the connectivity via VPN ourselves from different locations around the world.
Also looking into another possible cause with our provider right now as for certain actions we could reproduce the issue you are describing.
It might be related to the floods we recently had in Europe. There are still parts without power and some of the internet infrastructure has been destroyed completely.
You might be getting routed differently at the moment which could affect your connectivity to our servers.
Now, regarding your error, it sounds like an issue with your DNS configuration or cache.
Could you do a DNS flush and then try again the traceroute?
We are looking into the issue however on the first glance there doesn't seem to be anything wrong with the servers themselves.
Could you please provide us with a traceroute to the affected servers?
In windows, open the Windows search box and type in cmd and then open the command prompt.
In the prompt type in tracert URL and press enter. Take a screenshot or copy the result and post it here.
This seems to be related to a bug we had before on browser. The train buy screen should open again once you have researched the Bat.
We are on it to fix the bug, thanks for letting us know.
Can you elaborate on this? What happens if you try to buy a train?
What device are you on?
The current app is based on the old Flash version of the client and therefore becomes more and more incompatible with current technologies. We are working on a completely new version of the app based on our html5 client.
Unfortunately this is not the problem here. I already looked into the ticket and there is nothing wrong with the account or the avatar. Login works fine for us. So the account is not affected by the mentioned bug.
In general, the more cities you connected, the longer it will take you to load into the game because more elements need to be loaded.
Also, in general, our game doesn't cope well with any interruption to the loading process. It will just stop in its tracks, so to speak. Those can for example happen at home when connecting via wlan rather than cable or on route due to package loss.
So, the longer the loading time due to having a lot of cities, the higher the chance to encounter such an interruption and being forced to start loading all over again.
Changing this from our side would require a major rework of the system which is not only very time consuming but also quite risky. We are working on some other improvements (that us1 hasn't benefited of yet) that might help with the loading times in the future.