30%+ packet loss, constant disconnects--anything I can do or do I give up playing?
I've had unexpected disconnect problems in this game ever since November. It's always on the same hops, the ones that say NYC or New York, or the one immediately after, like on the screenshot below. It varies day to day. Usually at night there's up to 30% packet loss, and early in the morning it may be as low as 10%.
I can stay in town usually indefinitely, but as soon as I go into an instanced area with monsters, I'm usually kicked off a few minutes in--sometimes as little as 20 seconds. The packets are lost outside of my country, in the U.S., so my ISP can do nothing. What possibility do I have other than quitting the game? Can this be fixed in any way? I'm disappointed because I've spent over $150 dollars on this game, and I simply can't play it anymore. The disconnects get more and more frequent as the weeks go by. When I get disconnected I lose my portals and have to start the areas over, often losing the instances, which means the game is literally unplayable. ![]() Also, I've tried playing on the Australia gateway, where I get much higher ping, and I still get kicked off even without packet loss. The European gateway is not a possibility because the traffic still goes through NYC. Edit: Any plans for a South American gateway? Последняя редакция: Lord_Kamster#4909. Время: 20 февр. 2014 г., 17:43:20
|
![]() |
a text version of the WinMTR is better because then we can copy/paste things to point out to you.
first being that you're getting latency to your router. If you're using Wireless, try a different channel, or get closer. You want there to be no latency to your router at all. You might want to even try hard-wired to make sure there are no issues there. Beyond that, there is another large hop in the gblx network between the 8th and 9th hop. Notice the average latency goes from 26ms to 158ms? That's a pretty big jump.. not to mention that they go clear up to NYC to come back down to Dallas. Not sure why they do that. Either way it's a carrier/peer issue and the ISP is the only one who can do anything about that. I'd start with your personal network though and get that latency cleaned up there and then take another trace so we can see if it's just the ISP or anything else. I don't see any real packet loss however. You sent 111 packets and the destination received 111 packets. The stuff in the middle is mostly inconsequential. |
![]() |
Sorry for the image.
Anyway, it's a hard-wired connection going straight into my modem (no router). I ran a ping to it for a while the other day and I was getting like 300ms delays. I switched the cable and started getting better ping, 10-60 or so (I don't know if that variation is normal), so I figured it would help the problem... but it didn't seem like it. I ran a ping again now and encountered the following: ![]() Can I assume the modem is faulty, or is it perhaps my built-in ethernet card? Also, how many ms should it take to ping the modem? And should it be super stable or is a variation like I'm getting normal? It's barely like a 2-ft cable. Thanks for any feedback, I appreciate it. Последняя редакция: Lord_Kamster#4909. Время: 20 февр. 2014 г., 18:04:25
|
![]() |
Try rebooting your modem first.
There shouldn't be a lot of variation and the response times to the modem should always be under 50ms or so... even less if you're on hard-wired connection. Pinging my router I get under 1ms response times every time. 0.30ms to 0.37ms with very little variation. Notice that's UNDER 1ms. |
![]() |
I rebooted it and for now I'm not seeing that frequent loss, but the latency/variation is still there.
I may have a few spare ethernet cables in a box somewhere. Tomorrow after work I'll also dig out an old laptop I have and connect it to the modem, to see if I get the same result pinging it or not. Thanks for the help, I'll update once I've sorted this out. |
![]() |
If you know someone else with your isp, try lugging your machine to thier place and running the same tests. That can help determine if your router is faulty.
When it comes to your cabling, make sure to avoid any sharp bends and high voltage power supplies. IE: power bricks, flourescent lights, etc. If it has a transformer or a ballast, its hell for data cabling. HAIL SATAN!
|
![]() |
Also, check to see if there are updated drivers for your network adapter. (This helped in my case).
Read My Links!: http://www.theamazonbasin.com/forums/index.php?/topic/121389-read-my-links/
|
![]() |