"Maratsade, would you mind sharing the cities you saw along with your beam? Or at least give a rough impression of how far the cities were from the center of your beam?"
I'm on beam 68. Where's the center of this beam (as in, what city/town is closest)?
EDIT: Sometimes the "city" you get is "US."
maratsade wrote:"Maratsade, would you mind sharing the cities you saw along with your beam? Or at least give a rough impression of how far the cities were from the center of your beam?"
I'm on beam 68. Where's the center of this beam?
EDIT: Sometimes the "city" you get is "US."
Do you not get a city doing this?
From TestMy.net, select from the DB menu 'TestMy.net Database'
2. This leads to this display -- is there not a city shown?
3. Clicking the City leads to a display like this (the graph below would include all ISPs):
4. Clicking on the ISPs tab shows this:
This city is pretty far from me, but it does apear to be roughly in the middle of beam 82. I see in the past I had a different city showing, but it was in the same rough location.
The averages shown here are lowered by tests with the wrong test size, but it does appear to include my tests, since when I run a test, the count here increases. I do not know what they mean by '64 tests recently' perhaps 64 tests in the last week?
The average looks good -- about what I get a lot, and the impression is that others in this beam that happen to get this city are getting similar performance and therefore beam 82 is *not* over sold :-)
Beam 68 appears to be centered over northern VA, right near the border of WV -- I am just going by that picture someone posted a while back. I saw a link to some satellite page that shows spot beam positions more accurately, but I don't know much about it other than looking at it once or twice noticing the handful of spot beams J2 has down around Ecuador and in Mexico.
"2. This leads to this display -- is there not a city shown?"
Yes, different cities with different tests. I thought you wanted to know how far they were from the center of beam 68. The distances to what I think is the center vary, as do the distances from each of these cities and my location.
maratsade wrote:"2. This leads to this display -- is there not a city shown?"
Yes, different cities with different tests. I thought you wanted to know how far they were from the center of beam 68. The distances to what I think is the center vary, as do the distances from each of these cities and my location.
Yes, that was what I wanted -- it appears the city can be anywhere in the beam. I posted the above before I saw your reply with the distances.
If the cities are always within your beam, then it seems likely that the test results for HughesNet for the city are for users sharing the beam with you -- if the average is good, then the beam can not possibly be over sold, as obviously other users recently had scores high enough to raise the average given that many users are posting tests that artificially lower the average by using too small a test size, or by using Wi-Fi for the test. What we can not see is the overall average for the entire beam, since the numbers are divided up to the cities in the beam. Also, if the city can be anywhere in the beam, then some locations may be showing test results from J1/gen4 mixed in the results, depending on where you are.
Now, if we find a city showing in the above way that is nowhere in the beam foot print, then we can no longer think scores attributed to that city for HughesNet share your beam. My thinking is, if someone says they have an over sold crowded beam, then given the beam number, it is possible to find cities in that beam and review an average of other users that are likely in the same beam. If the average of recent tests good, it seems likely the issue is not that the beam is crowded since there has to be somebody with scores good enough to bring the average up.
"if the average is good, then the beam can not possibly be over sold"
But there may be other reasons for speed issues -- in 2017 there were problems with Bean 68 and the speed was pretty bad for a while and didn't get better until the engineers fixed whatever the issue was.
