Ask HN: Is there something wrong with internet right now?
Down Detector (http://downdetector.com/) is showing a huge spike in reports over the past 30 minutes. Many of our users are having trouble reaching our LB in Northern Virginia.
Anyone else having this issue or any insight as to what's going on?
77 comments
[ 3.0 ms ] story [ 155 ms ] threadNormally, ISP name resolution is the first thing I look at, but this seems atypical.
I've checked all the urls people said they had problems with so far (spotify, cloudflare, downdetector) and haven't had any.
Its really weird.
what the hell?
There are I think three threads talking about this right now. This one won the front page and topical title fight.
Sounds like an ISP issue.
AT&T (in Nashville) doesn't seem to be impacted; I'm RDP'd into one of my home machines with Uverse and everything's working great there.
[1] https://status.secondlifegrid.net/
Spamming `date` at an affected SSH connection suggests it's entirely a download problem, since all of the timestamps are very close, but they're received multiple seconds apart.
Like some other commenters here, my mobile connectivity is just fine.
EDIT: Certain sites (including Hacker News) are now qualitatively more accessible, and I'm now hitting expected speeds at http://testmy.net/download. SSH to my DigitalOcean is also better. Here's hoping everything else smoothes out soon!
Edit:
Sorta like this[0] I suppose.
[0]https://www.akamai.com/us/en/solutions/intelligent-platform/...
I haven't found a suitable replacement, would be interested to hear any suggestions.
DISAPPOINTED.
"Anyone having packet loss, please send traceroutes to the list. There is clearly something happening, but not much useful data yet. Some traceroutes might help narrow down the cause of the problem."
Some sites are easily available: Google, Yahoo.
Some sites are partially available: Twitter, Hacker News.
Many sites are completely unavailable: Down Detector.
Switched over to my VPN and haven’t had any problems since.
My initial pokes at the issues I was seeing were DNS related, but even switching the DNS hosts to Google or OpenDNS didn’t completely fix it. Maybe they’ve got some deep packet inspection issues?