grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY
edit:
May 3rd, @02:59PM
| reply to MMS747
Re: 4pm - 12am traffic shaping problem list
said by MMS747 :
There are patents and patent applications for methods and apparatus to do just that: Traffic Shaping. It is a management tool used throughout the industry, not just Hughes.
yessir, no one's arguing that. What I'm trying to slow down is the stampede of all the other non-technical customers who grab at every and all straws that might explain what the reason for THEIR particular connection issue.
In this case, the 4-12 thing seems very VERY selective. On this forum, there has been a teeny tiny (but very vocal) number of customers who have documented this particular Hughes phenomenon - and this is one of the LARGEST HughesNet self-help forums in existence. But even if I accept the figure of 500 complainants that somebody threw out here, that's STILL a drop in the half million customer bucket that is HughesNet.
So the KEY here is to come up with, is some common set of behaviors that might serve to trigger this 4-12 throttle for some - and NOT for others. And the survey info requested by the OP does NOT fulfill satisfy that requirement.
//greg//
--
HN7000S/74cm/1w/ProPlus - G16/1250H/Germantown - NAT 66.82.187.152/Gateway 66.82.25.10/DNS 66.82.4.12 and 66.82.4.8 - Firefox - AVG+Firewall v7.5 |
|
MMS747
@direcpc.com
| The number of customers affected couldn't be all that "teeny tiny." If you compare the normal speeds within the 4-12 timeframe with speeds outside the 4-12 timeframe, you'll see there isn't that big a difference anymore. In my own case, 4-12 downloads are typically 680+/- compared to outside 4-12 downloads of 700+/-. Once upon a time, the differences were quite marked. Given the huge numbers of 4-12 users, it stands to reason that more than a few users are throttled in order to maintain performance. |
|
MichaelRS
join:2006-06-10
Half Moon Bay, CA
edit:
May 4th, @01:25AM
| reply to grohgreg
Just a few fact points:
* The 4-12 throttle affects accoridng to HN Exec Cust Care Tech Whiz 75% of customers.
* HN has per the CEO 350,000 customers and hopes to get to 1 Million.
* While this forum may have a lot of visitors, clearly to be representative of 350,000 you would need more complaints.
* Any number of internet usage statistics will show clearly (null hypothesis etc.) that traffic on the internet or gateway is NOT a step function going on at 4 and off at 12, on the second, repeateadly.
* Such step function, as any gateway/network engineer can confirm, is man-made throttling by HN (see above) at gateway level, gateway = transponder. In fact several VARs have confirmed this practice being in place since years.
* Similar behavior was observed on DW4020 systems in 2006 and on Spot 21 of Anik/F-2 when WildBlue got wild in the west (and crashed) in 2007.
* Customers do NOT appreciate this business (! - not technical) practice, neither by HN, WB, ComCast or anyone.
* Unclear is if this practice is user specific throttling or gateway specific throttling. Any network engineers with a thought her ?
* Corporations pay people to observe and post on blogs on their behalf and undercover
* The following transponders have been reported as affected:
G17/74 - 1130/1250
AMC9/83 - 1430
AMC3/87 - 1330
G28/89 - 1070/1150/1270
G11/91 - 1410
G26/93 - 1216/1433
G16/99 - 970/1110/1210/1250/1370
SM6/113 -1150/1210
SM5/117 - 1070/1090/1130/1250/1270
* This 22 out of 70 transponders confirmed to be knocked out.
--
HN7000S - Satmex 6 - 1210 - 0.98m / 2W dish - HughesNet ProPlus |
|
MMS747
@direcpc.com | Interesting. Looks like someone's being doing their homework. Thanks. |
|
MichaelRS
join:2006-06-10
Half Moon Bay, CA
edit:
May 3rd, @11:27PM
| Yeah, welcome. Me engineer too.
Waiting for grohgreg to tell me it is all wrong, and he personally checked all transponders and there is no issue, but my checking satellites is using too much bandwidth, which is why I have the problems and am causing them for others 
BTW if anyone can actually confirm more satellites/transponders that would be VERY helpful.
--
HN7000S - Satmex 6 - 1210 - 0.98m / 2W dish - HughesNet ProPlus |
|
MonstaDriva
join:2007-09-02
edit:
May 4th, @12:31AM
| I was always on 89w 1270 till the 4-12 started . A couple of weeks ago they swapped me to 1070 and it was fine for 7 days . Then it started again . A few days later I got swapped to 1150 and it was fine for one full day then it did it too . So thats 3 of them . |
|
grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY
edit:
May 4th, @12:49AM
| reply to MichaelRS
said by MichaelRS  : gateway = transponder. Incorrect. At least the way that Hughes uses the term "gateway", it does not "= transponder". They use it in the sense of "gateway server", where each gateway has an IP address. There are typically six or more Hughes gateway servers per transponder. So the conclusions you based upon this misconception are not valid. Note PLEASE that I have listed my gateway server as part of my signature line. It's been there for years, and for good reason. You asked for people to identify their transponders - that will get you nowhere. If you want meaningful data, you need them to identify their GATEWAY address. And if members would compose a more informative sig line, you wouldn't even HAVE to ask.
A VAR may have one or more gateway address (servers), but I don't know of ANY that occupy a full transponder by themselves. They share, just like everybody else.
And with 2 thousand or more customers per gateway - and six or more gateways per transponder - I believe you're looking at individual customer throttling. Which brings us right back around to individual usage patterns.
Other than a few cases of overstating the obvious, I take little exception to the rest of your "facts". Although I follow Wildblue also, and don't have any idea of what you've identified as a 2007 "crash".
//greg//
--
HN7000S/74cm/1w/ProPlus - G16/1250H/Germantown - NAT 66.82.187.152/Gateway 66.82.25.10/DNS 66.82.4.12 and 66.82.4.8 - Firefox - AVG+Firewall v7.5 |
|
MichaelRS
join:2006-06-10
Half Moon Bay, CA
| WB crash = inability to add more customers (per spot), resulting in installers quiting business for them until their new bird is up. Exact same deal as with HN as they ran out of capital to add more capacity (ie more satellite). They claimed that their new satellite would fix it, but apparently it did not. What is scarry is that HN is using the same technology as WB does for SpaceWay and WB has issues delivering. Topline also the 9000 for HN does not seem to impress the customers.
--
HN7000S - Satmex 6 - 1210 - 0.98m / 2W dish - HughesNet ProPlus |
|
MMS747
@direcpc.com | reply to grohgreg
I'm pretty much convinced it's individual, based on usage patterns. In my case, I believe it was triggered by video streaming, especially YouTube. I also believe that not all video streaming will trigger it, but that there is a threshold. |
|
grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY
edit:
May 4th, @08:58AM
| reply to MichaelRS
said by MichaelRS :WB crash = inability to add more customers (per spot), resulting in installers quiting business for them until their new bird is up. Exact same deal as with HN as they ran out of capital to add more capacity (ie more satellite). They claimed that their new satellite would fix it, but apparently it did not. What is scarry is that HN is using the same technology as WB does for SpaceWay and WB has issues delivering. Topline also the 9000 for HN does not seem to impress the customers. That is the least supportable collection of sentences you have compiled yet. Such inaccurate representations of how this stuff works have now simply become counterproductive. There is not one technically rationally supportable sentence in that entire paragraph. But none of it has a single thing to do with this topic, I think it's probably best left to die from natural causes.
//greg//
--
HN7000S/74cm/1w/ProPlus - G16/1250H/Germantown - NAT 66.82.187.152/Gateway 66.82.25.10/DNS 66.82.4.12 and 66.82.4.8 - Firefox - AVG+Firewall v7.5 |
|
