Board Thread:General Discussion/@comment-110.159.130.178-20150914090037/@comment-26091666-20150917002812

@219.92.131.82 I am unfamiliar with other DMM games but if they connect to the very same IP address as the KC server you are on and that they all take the exact same route as indicated by both traceroute from your end as well as other traceroute sources then it sounds like maybe it is an issue with the actual kancolle game itself.

However to think of it on the contrary if such were to be the case you'd imagine all the players on that KC server would be facing issue and would be complaining on a very large scale and without giving insight as to which server they belong to. Do remember however that there are several servers that host Kancolle game, what you see from just a browser and playing naturally via DMM site is just the tip of the iceberg.

@NonayaDB For that short moment of when you ran traceroute and that there were no issues with it - presumably it would be safe to say that the game would have been working fine.

What I mean is that if the issues are really intermittent you need to pretty much be running traceroute every so often or at least build up enough background information spanning over at least a few days where you have noticed that your game session is giving you cat bombs.

As with KC3 (Kai), sure the information isn't terse enough but I consider that as a half way point between getting cat bomb screen and not knowing what is the cause of it to something like a full on network diagnosis.

@Both of you Another way to re-examine the situation is to re-route your packets so there is also the option of using proxy/VPN which in theory should notably alter the paths and therefore potentially bring a different sort of outcome.

What you would have also realised that if both of you take the same paths to the same destination (via traceroute comparison against each other) the use of other websites such as http://traceroute.org and their traceroute results may have indicated a different route taken. Again span that over a few days of constant monitoring may provide information as to where the source is potentially coming from.

Even if both of you took different paths to get to the same server at the other end with traceroute comparison against each other the results doesn't change the fact that there are plenty of ways to potentially reach from A to B.