ShinVector, on 05 January 2014 - 06:33 AM, said:
You can use notepad or what ever to save the info from WinMTR record the date and time. This is to create a log.
When your high ping issue hits, its should reveal at which hop the deviation is and where the problem starts.
Taking note.
Usually the first hop is your local network. If its goes bad there.. There is likely a local LAN issue.
Next few hops will be the local loop to your ISP..
After your ISP it will moving to other ISPs through the internet to reach MWO servers.
For eg.
I had own connectivity problem several months back which I was too lazy to troubleshoot and dismissed bad connectivity to Canada.
When I start troubleshooting I realise I was having latency spikes and packets loss even my own ISP's gateway IP on the local loop portion.
Problem found to be due to a loose optical fibre cable at the fibre terminate point in my living room where my FTHT optical fibre modem connects too. (Maybe one of cats did it who knows.)
Essentially want to avoid troubleshooting aimlessly if the problem is in your own house.
3000ms is kinda weird and extreme.. Try to log it down and know where the spikes are coming from as log from winMTR.
Ok shin, now we are all just lazy and the trouble is in our own house or local network....lol The more research i do on this issue, and the more persistent I am, the more it seems like its out of our hands and something else is going on.
a traceroute is good enough to tell these things. Its what these admins ask for. Spiking is spiking...its not a steady 800 ping for some of these europeans if the traceroute is showing them 250 or thats what their constant ping used to be. constant spiking like that would also show in the traceroute with an asterik.
I saw the guy from the phiillipines John E. quoted in this thread. He had a steady 800 ping, he wasn't even spiking. It was like he was being throttled. and spiking from in the 100s...to the thousands is already a non issue, beause the guy already has ping in the high 100s to being with!
Care to comment on the links i posted, which show this exact issue also happened back in january immediately after MWO had some downtime and released a new patch?
Apparenlty MWO has that many players that play immediately after a patch that it overloads most ISP's circuits? I'm finding it harder and harder to believe man. Something is fishy about this.
I still say either something is going on to try and level everybodies ping in the game actually doing more harm. maybe its a jealous malcious user... anything is possible to me at this point. Or pgi doesn't pay enough for bandwidth or dont' rate as a small company.
Or its just an issue routing to canada for most isp's, especially during the winter months when there is more load.
I don't think there is much we can do about it on our end. I doubt the admin from germany is going to reply back to me...and this time that server isn't actually owned by verizon. SO me constanlty harassing verizon, like believe me I've been doing, isn't really going to get me anywhere. The circuit on that router in question now is an internap circuit and the router is owned by tiscali/tinet.net.
Either way its mind boggling and this is the only game anybody has issues with. maybe they should host in toronto, I dunno what would fix this.
Edited by RichAC, 05 January 2014 - 07:01 AM.