Leaderboard

It has been a while since my last visit in this particular forum, as some of you know I got rid of hughenet a long time ago for DSL. Anyway, I thought I would come back and see the complaints on Hughesnet, but to my shock, no posts since 2012! So, either Hughesnet have got better at what they do (highly unlikely) or they have less users to complain about the service or maybe people have got used to what they have. Either way, just dropping into an old haunt to say hi!

TraceMy isn't really doing a test, it's a logged traceroute... it's just conducted regularly. TraceMy is activated as soon as you hit any page outside of the forum (currently tracing only registered users... only beta testers and a handful of others have been granted access to see the data). It's currently only running on my main server but this will expand soon. I'm working on to make this do much more... the reason I haven't fully released it is because, first, I'm not done. Second, I'm still trying to understand what I've built. So far what I'm gathering is that you're not looking for hops that just have long response here and there... you're looking for hops that continually have longer response times. Especially should be noted if the hop responds that way more than three consecutive times. There really is no frequency to testing. You're tested as soon as the queue runs. It queues over and over and is based on your activity on TestMy.net. Every page load (again, outside of the forum) resets your time to 2 minutes, if you stop interacting with the site... it stops interacting with you. For that two minutes you'll be traced over and over as you reach your place in line. No set time, it just runs when it's available. This is done server-side and all you need to do to activate it is open TestMy.net. It's silent and you can surf the site as you normally would, that side of the program actually has nothing to do with what you see on your screen. (it's pretty nifty) What I'm finding is that just because you're displaying horrible speeds... doesn't mean that it's going to show in the trace. Also, just because a hop responds slow... doesn't mean that your speeds will be degraded. Check this out... here's an example using my own connection. I obviously have a fast connection at home, it runs awesome... all the time. Now look at the trace results about 2 minutes before my 12:35p test. (hop 9 for me is the end of trace by the way but is not my actual IP...) Yeah, that had a long response... if there was any issue during that time it wasn't noticeable to me. I wasn't testing at that exact moment so who knows, it may have resulted in a little bobble. Obviously you'd like to see nice even response times but for a hop to respond like that here and there... no worries, it happens. Some routers de-prioritize ICMP traffic so it's normal in some situations to see spikes here and there. But if a hop is continually doing that, especially in succession... there is most likely something going on with the hop. Before I release it publicly I'll do a full writeup and I'll cite logged examples displaying what the real problems look like. Here's a little example I randomly pulled (username sistem) of what MAY be an issue. See the top blue line, that's hop 7 of 8. It often responds slower than the final hop, and does it consecutively. It also seems that when that happens it sometimes causes the final hop to respond slower.... Now look at this members result around the same time... dropped to half of his average. Going back further in his results I find that when he has a lower than average result... it's often accompanied by slower than average response on those hops. This is not always the case. But if you if you experience slower than average speeds then look to your TraceMy results it can help determine what part of the route is possibly at fault. Now, looking at your TraceMy.net results... I don't see anything alarming or stand out. Researching the times when you display slower results shows very normal traces. Sure there are spikes, but they don't correlate with those times... and they don't consecutively respond bad. Like I said, just because there's an issue with a hop/router doesn't mean that it's going to respond bad and vice versa. But when you start to see regular patterns, it can be a good indication. ... as soon as I understand what I've built better and can put it all into words I will. I'll also tell the program to look for the known patterns I'm finding and alert the user to a possible issue. I'm also developing more in depth analysis of the route... realize that I only have a couple of days of programming time invested in that so far. Right now it's in a gathering phase so... again... I can understand what I've built. (gee, you think that's enough ellipsis for one post, lol... ... ...)