The fact that it's only in Chicago makes me think it's an AT&T error e.g. with BGP or internal routing rather than something intentional.
We have our four core ZeroTier root servers on different providers at different data centers for this reason. Entire data centers or cloud regions becoming unreachable from a certain ISP in a certain area for a period of time is not all that uncommon.
In case you don't know: the core of the Internet is basically a ball of chewing gum, duct tape, glue, twine, and carrier pigeons maintained by grumbling BGP admins.
I'm not clear that this is actually a Net Neutrality issue rather than a routing issue. Perhaps there is a way to solve this with DNS, routing connections to a different place. Maybe this is a failure of the infrastructure that supports the service. Use DNS to help ATT get connections to the right place.
Well, with AT&T being caught red handed installing stealth connections in their network for the NSA years ago- - - it's a "shoot first, ask questions later mentality" against AT&T.
Yes I saw, I'm one of the boingboing users mentioned. I don't have a discourse account yet, but if there's any info I can provide to help resolve this, I am happy to do so. Intend on signing up soon to monitor on meta.
24 comments
[ 5.3 ms ] story [ 66.0 ms ] threadWhat's special about Chicago?
We have our four core ZeroTier root servers on different providers at different data centers for this reason. Entire data centers or cloud regions becoming unreachable from a certain ISP in a certain area for a period of time is not all that uncommon.
In case you don't know: the core of the Internet is basically a ball of chewing gum, duct tape, glue, twine, and carrier pigeons maintained by grumbling BGP admins.
[1] https://en.wikipedia.org/wiki/Hanlon%27s_razor
The available evidence (only being blocked in Chicago) would actually point to a technical issue as opposed to an intentional block.
Sounds more like a routing misconfiguration that AT&T can't pin down.
BTW, if these tutanota guys were smart, they'd be pitching their services to AT&T instead of dragging them through the mud.
Last I checked, AT&T had subcontracted Yahoo as their mail handler. Nowhere to go but up from that mess...
Traceroutes to it and www.tutanota.com seem to die in similar or the same place.
2001:1890:ff:ffff:12:122:2:225
Which both last end there currently. Last two not octets were different. Few minutes ago.
I don't know enough about ipv6 to diagnose further, or how to force my phone to ipv4 on lte.
We are tracking it here https://meta.discourse.org/t/cannot-reach-one-forum-on-at-t-...
https://meta.discourse.org/t/cannot-reach-one-forum-on-at-t-...