*checks the outages mailing list*

well the Comcast issue that @alyx@witches.town just mentioned has a thread

https://puck.nether.net/pipermail/outages/2017-November/010891.html

I suspect it's not just Comcast having issues though

@staticsafe this any help? I don’t know how to read all of it, but http://www.internettrafficreport.com/namerica.htm

@gannet not particularly, mostly because that site has hosts that are no longer around and hasn't been updated with new ones in a while AFAIK

@staticsafe ah. Well, that's frustrating. (Shows how dated some of my experience is...)

so it's basically confirmed at this point that it's a Level3 transport issue

the reason I can still use my Mastodon instances is because it's going over IPv6 which is going over the HE BGP tunnel which is taking a HE path

@staticsafe ipv6 🙏

@staticsafe looks like someone has helpfully made a status page to track this issue: https://islevel3down.com/

so a theory from Job Snijders as to what happened:

"These more-specifics win over less-specifics, so the world's traffic to comcast
may now be flowing through level3, and maybe there is not sufficient bandwidth
capacity available on those Level3<>Regional_Comcast interconnections."

https://puck.nether.net/pipermail/outages/2017-November/010947.html

(it is resolved now as @alyx@witches.town just mentioned)

*wonders if the folks over at BGPMon can confirm that theory*

so yeah BGPMon confirmed it:

"BGP routing issues between @Level3 and @comcastcares caused large scale network service degradation in North America between 17:50-19:20 UTC"

https://twitter.com/bgpmon/status/927644791315185665

#networking

@staticsafe so you're saying i narrowly avoided awoo.space being down because i set up ipv6 on my new instance?

sicknasty

@vahnj @staticsafe heck yeah!!!! new internet technologies!!!!

@staticsafe
Level3 has always been pretty squirrelly in my experience. My old instance would become inaccessible at times because of them