Kevin Beaumont:
»The Facebook outage has another major impact: lots of mobile apps constantly poll Facebook in the background = everybody is being slammed who runs large scale DNS, so knock on impacts elsewhere the long this goes on.«
https://twitter.com/GossiTheDog/status/1445118907187175427Oh my gosh, their IPv6 address contains "face:b00c"...
> 2a03:2880:f0fc:c:face:b00c:0:35
Besides being fun and quirky, it is actually useful for their sysadmins as well as sysadmins at other orgs.
Well at least it will in 2036, when IPv6 goes mainstream.
Re:Facebook-owned sites were down
by forgotpwd16 on Tuesday October 05, 2021 @02:43AM
(#28756187)
How difficult is to get such a "vanity" address?
You just need to get a large enough block so that you can throw most of it away by adding your own vanity part to the prefix you are given. IPv6 really isn't scarce so you can actually do that.
Re:Facebook-owned sites were down
by willstrafach on Tuesday October 05, 2021 @12:17PM
(#28761490)
The face:b00c part is in the Interface ID, so this did not even need a large block (Though I am sure they have one).
Re:Facebook-owned sites were down
by mikefromhome on Monday October 04, 2021 @04:37PM
(#28751765)
dead beef sounds about right
% traceroute -q1 -I a.ns.facebook.com
traceroute to a.ns.facebook.com (129.134.30.12), 64 hops max, 48 byte packets 1 torix-core1-10G (67.43.129.248) 0.133 ms
2 facebook-a.ip4.torontointernetxchange.net (206.108.35.2) 1.317 ms
3 157.240.43.214 (157.240.43.214) 1.209 ms
4 129.134.50.206 (129.134.50.206) 15.604 ms
5 129.134.98.134 (129.134.98.134) 21.716 ms
6 *
7 *
% traceroute6 -q1 -I a.ns.facebook.com
traceroute6 to a.ns.facebook.com (2a03:2880:f0fc:c:face:b00c:0:35) from 2607:f3e0:0:80::290, 64 hops max, 20 byte packets
1 toronto-torix-6 0.146 ms
2 facebook-a.ip6.torontointernetxchange.net 17.860 ms
3 2620:0:1cff:dead:beef::2154 9.237 ms
4 2620:0:1cff:dead:beef::d7c 16.721 ms
5 2620:0:1cff:dead:beef::3b4 17.067 ms
6 *
7 *
8 *