3 ms·
It barely copes with cloudflare/Aws having a Hiccup
by Havoc 4y ago
It barely copes with cloudflare/Aws having a Hiccup
- wolfi1 4y agothat's not the Internet as a whole, is it? only http[s]-services are affected by that. in case of a nuclear attack I guess every service will be affected
- iso1631 4y agohttp? My website runs fine if amazon and cloudflare go down. However as I'm in the UK, a large nuke in Docklands would cause big problems. Most of my company's connectivity reaches the world through Telehouse and Sovereign House, both in Docklands, about a mile from each other. A large nuke landing on top of the Blackwall Tunnel - perhaps on top of Switch (another major building we have), would probably knock both out. You could effectively knock out the UK's internet by sabotaging the Thames Barrier, let alone the damage just a single nuclear bomb in docklands would do.
- Havoc 4y agoIf London gets hit then I'm more concerned about whether there is a functional world economy left.
- dylan604 4y agoWell, if we were going to attack the internet with nuclear weapons, how many data centers would need to be targeted? Seems like if we just threatened us-east-1, it would shutdown and save us the nuke. Switching regions to us-west-1 might actually need the ordinance to be expelled, but it might go down after us-east-1 fainted. Not really sure about cloudflare data centers, but targeting the location of 1.1.1.1 might be a lot of bang for the buck. Let's not forget Goog's 8.8.8.8 and family. How much of routing would then happen after that first strike? How many other centralized places of the decentralized internet would need to be targeted in the first strike?
- tristor 4y ago> targeting the location of 1.1.1.1 might be a lot of bang for the buck. Let's not forget Goog's 8.8.8.8 and family. 1.1.1.1 and 8.8.8.8 are anycasted addresses, they don't have one location, and the location you are connected to differences based on your location. Anycast was one of the earliest things formalized by the IETF and originally created in 1989 as a method of addressing using IP, /specifically/ for resiliency and performance.
- dylan604 4y agoThis is way too serious of a reply to my not obvious enough tongue in cheek comment, but now I've gone and learned something new with Anycast being an actual system on the inner workings of the interwebs