[Info-vax] Facebook service outage

[chris]

On 10/04/21 22:33, Simon Clubley wrote:
> On 2021-10-04, Stephen Hoffman<seaohveh at hoffmanlabs.invalid>  wrote:
>>
>> Facebook, Instagram, Facebook Messenger, WhatsApp, Login with FB, etc.,
>> are all offline.
>>
>> The Facebook IP address space and all its services are inaccessible.
>>
>
> I guess someone took the move fast and break things mantra literally. :-)
>
> Is anyone seeing the actual DNS entries for facebook.com disappearing
> as well ?
>
> Depending on which DNS server I use, I either get the entries or a
> SERVFAIL from nslookup.
>
> Does anyone else see this ?
>
> Just tried it from Eisner as well. This is what I get:
>
> $ nslookup
> Default Server:  dns.google
> Address:  8.8.8.8
>
>> facebook.com
> Server:  dns.google
> Address:  8.8.8.8
>
> Non-authoritative answer:
> Name:    facebook.com
> Address:  157.240.220.35
>
>>   Exit
> $ nslookup facebook.com 4.2.2.2
> Server:  b.resolvers.Level3.net
> Address:  4.2.2.2
>
> *** b.resolvers.Level3.net can't find FACEBOOK.COM: Non-existent host/domain
>
>> Reportedly, this outage is due to erroneous BGP routing announcements.
>>
>
> Let's just hope it's an internal screwup and not an external attack.
> The consequences in the latter case might be rather interesting.
>
>> Reportedly, internal access including badges and badge readers and
>> building and door access controls are all offline, and remote access to
>> their peer routers is also all offline.
>>
>
> Someone has some lessons to learn about not making all systems depend
> on each other. Internal access should not have been affected by this
> in a properly designed system IMHO.
>
>> This looks to be one of the biggest service outages around, and with a
>> detail?the BGP routing announcements?that y'all might want to consider
>> within your business continuity and business recovery plans.
>>
>
> Simon.
>

nslookup fails here as well, so looks likes it might be a dns hack...

Chris