About Matthew Maples

I'll say for a little longer until the new satellite is operational and see if our data caps increase in line with the satellite capacity increase. If they don't then I'm jumping. Already paying near $75 to HughesNet every month for 10GB, and for that I can't even look at Youtube or stream music or videos from Amazon Prime or use any on demand services. That's getting old. ... View more

I think I'll post this here. I'm still having packet loss across the board. I sent a support ticket to Arena Net, as I was experiencing issues in Guild Wars 2 again, and they told me to run a program called WinMTR to monitor my network connections. This was the result after 30 minutes: The % is the amount of dropped packets,  sent and received are the number of packets, and the last four are pings in ms. This was their email below: GM MagicalPotato (Guild Wars 2 Support) Apr 18, 16:00 Hello, Thank you very much for the information as this does appear to show the issue you are having. According to this report, your connection is suffering from packet loss. If you are not familiar with this term, it simply means the loss of data while in transit from point A (your computer) to point B (our servers). What this means is that either not enough information was received by our servers, the information that was received was corrupted, or it wasn't sent at all. So how does this affect you? In-game: The game is trying to adjust your position to your last known location or attempting to re-send that data over and over, but too much is being lost in transmission. Now, because Guild Wars 2 is a client/server setup, the server is always considered right (this is a security measure to prevent cheating/hacking). Thus, the game is forced to adjust your location to where the server last thought you were. This causes your character or NPC's to "snap back" or "rubberband" between the two sets of information (one set from your client, another from the server). Since they are fighting (in a manner of speaking) over who is right, your character or NPCs will appear to teleport back and forth while this "fight" for control happens. Then, if not enough data is received over time, the game will likely disconnect you because it thinks you are no longer active. Installing and/or updating: In terms of installation or updating the game client, the data being sent to patch your client is becoming corrupted if it arrives, or simply not arriving at all. This prevents you from obtaining the patch files intact. Thus, the download either has to keep retrying over and over to get valid data, or it simply errors out and stops the installation if enough attempts to get the information fail. Because the loss of data is happening prior to it reaching our game servers, you will need to contact your Internet Service Provider for assistance. I would highly recommend sending them these results so they can visually see the issue you are suffering from. Please do not hesitate to contact us should you have any additional issues, questions or concerns. Regards, GM MagicalPotato Guild Wars 2 Support Team http://help.guildwars2.com/ ... View more

I am as well. I bought a new phone and it turned on WiFi by itself and downloaded about 800MB worth of updates before I caught it. Plus it'd be nice to be able to use my Amazon Prime Video and DirecTV Video On Demand at least somewhat. ... View more

Haven't noticed any packet loss in a couple of weeks, and my primetime pings are back to normal, so I guess the engineers fixed the problem. Can't wait until the new satellite is online and our data caps increase... ... View more

Why can't I get this all day long? ... View more

Another bright, sunny, clear day, same packet loss. ... View more

Here's a good one. And no my dish is not icy or snowy, and the skies are clear and near full moon out. ... View more

Packet loss is back too. ... View more

64.25.33.34 is one of the IPs of the server, there's many of them in Texas. ... View more

Been better, pings in the 800s but at times going into the 1200s and spikes of higher ones. I don't use Skype, not on a 10gb allowance. ... View more

Still getting bad times (left) with times of what it should be (right). No packet loss though. ... View more

I thought I was already switched to that plan the last time I had problems, but if it's the same price then I'll switch, just don't do it for about 3 hours if you can. ... View more

Since I posted my last message I've only had a few hours of problems combined. Average pings are still averaging in the 800s with times spent in the 1000s, but there hasn't been any packet loss. ... View more

Everything's been perfect the last 3 days, no packet loss, no excessive pings, but today I am experiencing the same packet loss issue again. ... View more

And then there are times I get great pings, but the packet loss causes problems. ... View more

This is about what it should be, but the problem is I don't get this very often, only a very small percentage of the time, and it's mixed in with ones like what I've been getting for TWO MONTHS. ... View more

After working fine for the past 2 days (pings around 650ms, no packet loss), packet loss is back ... View more

Hope to have a solution soon. ... View more

Sadly no. ... View more

Spent the last couple of hours running this test. ... View more

Here is a log from the same utility run after my last post. For this test the Time Out threshold was set to 10000ms and count upped to 100. As you can see, I am still getting packet loss, and that's the main cause of problems. It defaults to using the Google DNS server since it is a known stable, fast target. Ping statistics for 8.8.8.8:     Packets: Sent = 100, Received = 96, Lost = 4 (4% loss), Approximate round trip times in milli-seconds:     Minimum = 565ms, Maximum = 1564ms, Average = 696ms And here is another ran just after that one, with the count dropped to 50 (timeout period was kept at 10000ms): Pinging 8.8.8.8 (with 32 bytes of data): Reply from 8.8.8.8: bytes=32 time=695ms TTL=55 Reply from 8.8.8.8: bytes=32 time=905ms TTL=55 Request timed out. Reply from 8.8.8.8: bytes=32 time=930ms TTL=55 Reply from 8.8.8.8: bytes=32 time=729ms TTL=55 Reply from 8.8.8.8: bytes=32 time=649ms TTL=55 Reply from 8.8.8.8: bytes=32 time=703ms TTL=55 Reply from 8.8.8.8: bytes=32 time=599ms TTL=55 Reply from 8.8.8.8: bytes=32 time=602ms TTL=55 Reply from 8.8.8.8: bytes=32 time=628ms TTL=55 Reply from 8.8.8.8: bytes=32 time=627ms TTL=55 Reply from 8.8.8.8: bytes=32 time=576ms TTL=55 Reply from 8.8.8.8: bytes=32 time=619ms TTL=55 Reply from 8.8.8.8: bytes=32 time=604ms TTL=55 Reply from 8.8.8.8: bytes=32 time=585ms TTL=55 Reply from 8.8.8.8: bytes=32 time=647ms TTL=55 Reply from 8.8.8.8: bytes=32 time=666ms TTL=55 Request timed out. Reply from 8.8.8.8: bytes=32 time=587ms TTL=55 Reply from 8.8.8.8: bytes=32 time=608ms TTL=55 Reply from 8.8.8.8: bytes=32 time=633ms TTL=55 Reply from 8.8.8.8: bytes=32 time=719ms TTL=55 Request timed out. Reply from 8.8.8.8: bytes=32 time=602ms TTL=55 Reply from 8.8.8.8: bytes=32 time=893ms TTL=55 Reply from 8.8.8.8: bytes=32 time=910ms TTL=55 Reply from 8.8.8.8: bytes=32 time=627ms TTL=55 Reply from 8.8.8.8: bytes=32 time=579ms TTL=55 Reply from 8.8.8.8: bytes=32 time=612ms TTL=55 Reply from 8.8.8.8: bytes=32 time=621ms TTL=55 Reply from 8.8.8.8: bytes=32 time=863ms TTL=55 Reply from 8.8.8.8: bytes=32 time=867ms TTL=55 Request timed out. Reply from 8.8.8.8: bytes=32 time=857ms TTL=55 Reply from 8.8.8.8: bytes=32 time=691ms TTL=55 Reply from 8.8.8.8: bytes=32 time=766ms TTL=55 Reply from 8.8.8.8: bytes=32 time=607ms TTL=55 Reply from 8.8.8.8: bytes=32 time=806ms TTL=55 Reply from 8.8.8.8: bytes=32 time=692ms TTL=55 Reply from 8.8.8.8: bytes=32 time=817ms TTL=55 Request timed out. Reply from 8.8.8.8: bytes=32 time=614ms TTL=55 Reply from 8.8.8.8: bytes=32 time=670ms TTL=55 Reply from 8.8.8.8: bytes=32 time=600ms TTL=55 Reply from 8.8.8.8: bytes=32 time=585ms TTL=55 Reply from 8.8.8.8: bytes=32 time=615ms TTL=55 Reply from 8.8.8.8: bytes=32 time=641ms TTL=55 Reply from 8.8.8.8: bytes=32 time=617ms TTL=55 Reply from 8.8.8.8: bytes=32 time=588ms TTL=55 Reply from 8.8.8.8: bytes=32 time=696ms TTL=55 Ping statistics for 8.8.8.8:     Packets: Sent = 50, Received = 45, Lost = 5 (10% loss), Approximate round trip times in milli-seconds:     Minimum = 576ms, Maximum = 930ms, Average = 614ms ... View more

No change. Still 1500ms pings in game (vs 700ms before November) with higher spikes. Web response is still elevated to over 2000ms at times. My wireless card's ping tool shows the wide variability in times. ... View more