It's been a while since we last heard from you, so we will close this thread. If you still have concerns, please start a new thread and include a detailed explanation so we can better assist you.
I have been dealing with this problem since my installation back in April. I have had enough! Last night I called and asked for my equipment to be pulled out of here, but was talked into one more chance for engineering to attempt a fix. For instance, I just ran a series of 5 tests (25M down/4M up} and got results ranging from 13.9 to 22.4M down and 1.6 to 2.1M up. Why such a large variance over a 25 minute time frame?
Last night I was running in the 1 to 3M down range. Same weather conditions; no other variables that I can see.
What GabeU is suggesting regarding only one device being connected, and for that one device to be connected via Ethernet cable is not a "real world" condition for me, nor would it be practical in my case. I don't recall these parameters being specified in the sales pitches in order to get me to sign up.
No offense meant Gabe.
swjohnson wrote:
What GabeU is suggesting regarding only one device being connected, and for that one device to be connected via Ethernet cable is not a "real world" condition for me, nor would it be practical in my case. I don't recall these parameters being specified in the sales pitches in order to get me to sign up.
Troubleshooting is not meant to mimic a "real world" condition, for you or anyone else. It's troubleshooting. It's meant to discover the cause of a problem. As alluded to by maratsade, testing when directly connected gives a baseline result, without which troubleshooting is not as precise and can be a much more tedious task. Testing with a direct connection is the most basic connection there is. The fewest moving parts, if you will. Testing via WiFi doesn't tell you whether the speed problem is with the actual service, the WiFi, or the device the WiFi. WiFi connected devices are susceptible to a multitude of different things that can affect speed. A baseline connection isn't. Troubleshooting is a process of elimination.
When your Verizon home phone service is having an issue the phone guy doesn't troubleshoot with your cordless phone, nor ANY cordless phone. He directly connects to establish whether the problem lies with Verizon's service. If not, he checks the lines in your home. If not, he checks your cordless phone. He doesn't start with your cordless phone, even though that's what you use every day. And Verizon was chosen arbitrarily for the purposes of my example. I don't know what home phone service you have, nor that you even do.
swjohnson wrote:
No offense meant Gabe.
None taken. Perhaps you now better understand why speed issue troubleshooting is performed the way it is.
Edit: By the way, the variance in the speed of your service is most likely due to customer load on your beam and/or gateway, which varies from one moment to the next. This is one of the reasons why speed cannot be guaranteed. You speed will tend to be most affected by customer load in the evenings.
If YOU would like to take advantage of the help on this Communinty for your speed issues please start a new topic to begin the process of figuring out what's going on.
