Leaderboard

I notice that the time shown in My Results shows the correct time (for my location) of the individual tests. When I export the result (to .CSV and then as .xlsx) the generated timestamp in Column A shows the time as one hour later. This must be some bug to do with daylight saving? I do not need to know the reason, but I would like you to fix it. I have attached relevant screen shots. Thank you. MarcelVH. 2020-05-07-Time-Discrepancy-in TestMyNet.docx

@CA3LE you may have to answer this one. His results are 2005-2006

That does look incredibly similar... But wouldn't that also show up on a test within the ISP's network? Because my issues only show up as soon as the data leaves the Buckeye network - which is why they're refusing to so much as acknowledge there is an issue, much less do anything about it. For example, my most recent tests. These were performed at the same time - one here: (https://testmy.net/db/qqsHYdzLe) and one on Buckeye's network: (http://buckeyebroadband.speedtestcustom.com/result/4793d4b0-7b42-11ea-a918-afd21c61947b). If it was a signal noise issue, wouldn't it show up at least intermittently on the intranet test as well? Also, my cabling hasn't been touched in a decade (and the router has already been replaced in the hopes of fixing the issue), so if it was anything to do with my wiring, wouldn't it have shown up even longer ago than this? As far as I'm aware, coax cable doesn't degrade over time - or am I mistaken? Also, how would that square with the issue that brought me here in the first place, where my speeds had initially been sustained for hours at a time at low speeds, then hours at a time at high speeds? If it were signal noise, that couldn't have happened, am I right? This, for example: Thank you for your response, @nanobot!

You might want to have a tech come out with a signaling meter. I had Spectrum send one out Tuesday morning, and my tests went from all-over-the-place to consistent 90-120Mbps. (I pay for 100Mbps and was seeing around that before.) I was getting the same thing you are right now: some tests would come back at 2-10Mbps, some at 100Mbps+. Latencies did the same weird spikes. It turned out that the way they ran my cabling introduced a lot of noise, two bad junctions, and cost me huge signaling levels. The thresholds were red-red-red on his meter when he got here, then after doing a couple quick mods it was blue-blue-blue. I was seeing 10-20% packet loss Monday, now I see <1% packet loss. (It also didn't help that my modem was old-old and one of those "combination" / modem+router+wifi units...the new modem is just a modem.) Here are my results for the last week. That last drop was just before he showed up. This also doesn't include the tests I aborted because things just hung.

It’s a pain to have to go thru this stuff I know. I suggest you call them instead of emailing. Be polite but persistent. If you don’t get satisfaction from talking to their first level support person, ask to speak to a supervisor. I assume you have some kind of problem ticket number that your emails are posting to.

The first few hops of your Trace Routes appear to rule out the connection between your router and the ISP, so it does not appear to be an issue with your home network, router or its link. Besides the excessive ping times, your ISP appears to have very high packet loss going by the number of individual stars. Three stars in a row just means the gateway at that hop does not respond to ping requests, so you can ignore those. For comparison, these are trace routes to 1.1.1.1 and 72.30.35.10 from my end, which is over a 4G cellular connection: Try a "ping -n 100 1.1.1.1". Ideally this should finish with a "0% loss" and no more than 1%. High packet loss (3% or higher) will cause a drop in throughput as your connection will spend much of its time re-requesting packets that did not arrive.