Earlier quoted context omitted.
There was an irregularly but often transmitting radio antenna tower fifty feet from my home, and the outage duration when an outage occurred was precisely the same each time, because Docsis is very carefully specified in how it starts up. (Don’t remember the duration, sorry.) The outage interval varied based on antenna usage; if OP is suffering a similar circuit break, a continuous transmitter nearby could certainly…
The outages mostly happened at very specific times during the hour (:29 and :44) for 17 months. It just doesn't add up to being RF interference, especially from a radio tower. But if OP has a radio tower 50 feet from their home, I guess we could consider it. How did you know when the radio tower was transmitting?
A monopoly ISP refuses to fix upstream infrastructure
111–120 of 361 posts
Re: A monopoly ISP refuses to fix upstream infrastructure
#112Re: A monopoly ISP refuses to fix upstream infrastructure
#113I got a problem with my AT&T Fiber service at the house. We pay for a 500 Mbps plan, and I can get 600 Mbps up and down via ethernet on speedtest (probably due to over provisioning). However, I can only download stuff about 8 MB/s from most places. I believe this to be an internal issue as whenever I connect to any VPN service, I can get the full 600 Mbps. Furthermore, some servers are able to serve me at full speed,…
Github is still famously IPv4 only. I don't know if there is a split between the SSH (if you use SSH to access the repos) and HTTPS (the tarballs) setup on their end, so maybe you get full speed on IPv6 and limited on IPv4 (or the other way around). Try disabling IPv6 on your end, if the speeds match then this might be it. If IPv6 is fast using an IPv4 gateway that tunnels via an IPv6 VPN might be a workaround.
I also had a similar problem a while back. Some speedtests showed more bandwidth than I could get in regular HTTPS downloads. I could get multiple downloads running at the same time that in total added up to the expected speed. In my case the line was just lossy enough (TCP retransmits in Wireshark) for TCP to never scale up its window size properly beyond a certain limit per connection. I verified this by running iperf in TCP and UDP against a gigabit server, UDP reached near full speed because it didn't care about a few lost packages. Working around that issue might be a bit harder, maybe [1] via [2] can provide some ideas to look into.
Re: A monopoly ISP refuses to fix upstream infrastructure
#114I've been through this multiple times. A lawyer friend of mine told me that in such cases only going through a legal battle would solve the problem but the amount of money and time for the zero return will get no interest of any lawyers.
You'll be out of luck unless yourself are a lawyer or you know someone being affected who is up to this tedious battle
Re: A monopoly ISP refuses to fix upstream infrastructure
#115Earlier quoted context omitted.
I'm not so sure that's an accurate diagnosis. But I agree it's certainly better than one can get from phoning support.
I can't speak to the accuracy of the diagnosis, but the claims about NTP are bizarre, and to the best of my knowledge, wrong. There's nothing specific about the times the incidents cluster around that would have anything to do with NTP. It doesn't work like that.
Re: A monopoly ISP refuses to fix upstream infrastructure
#116Earlier quoted context omitted.
[flagged]
I think this is a lazy criticism that I am _also_ growing tired of. If LLMs are trained on written information, that pattern of speech was present before they got there. It's a good way to add emphasis.
Re: A monopoly ISP refuses to fix upstream infrastructure
#117This has to be the weirdest post I've seen in a while? Cable infrastructure in the US is awful. I can't imagine a scenario where it would be reliable.
https://en.wikipedia.org/wiki/January_1998_North_American_ic...
A lot of the Northeast US that was impacted has fairly 'fresh' copper infrastructure in the last 20 years.
... but in reality, yeah. The outdoor plant does not get taken care of well (in general), there's only so many field techs to go around to be able to re-balance an entire RF system and its nodes.
Re: A monopoly ISP refuses to fix upstream infrastructure
#118Earlier quoted context omitted.
[flagged]
I think this is a lazy criticism that I am _also_ growing tired of. If LLMs are trained on written information, that pattern of speech was present before they got there. It's a good way to add emphasis.
It feels like AI has suddenly given a platform for people who previously were unable to properly write blog content. But it immediately feels unoriginal and generic.
I’m just not interested in that type of content and immediately put off by it.
The only reason I mentioned this is because of the comment about Gemini 3 being in the comments.
I’m just really, really tired of all the AI content everywhere nowadays and crave some authenticity.
It just feels like cheap remakes / imitations to of original content.
Re: A monopoly ISP refuses to fix upstream infrastructure
#119Re: A monopoly ISP refuses to fix upstream infrastructure
#120Earlier quoted context omitted.
I was merely pretty sure that the comment was AI generated as I read it. After reading it, I became a lot more confident when I noticed the username above the comment: Gemini 3 . Is this a Wordpress plugin the blog author is using?
[flagged]