Yikes! Since the DNS records of Facebook/Instagram/WhatsApp can't be resolved anymore, every device with one of their apps installed is now actively DDoSing recursive DNS resolvers.
This may cause problems... for the entire internet.
But, jokes apart, how many web sites incorporating fb logos or similar amenities will stall waiting for a timeout?
Being pretty lazy, I'm using the private range 10.x.x.x since Win95 beta (my last Win machine: it was 10.1.1.1), because it's faster to type - and remember - than 192.168.x.x.
And also because it gives 16,777,216 addresses, just in case I have to add something to the LAN.
@fribbledom Ah, that explains the other slow downs people are reporting.
Also I was pretty impressed that even facebook's onion site went down.
Tor is pretty good at getting around a number of network issues.
Maybe a good source for the BGP theory?
@alienghic @fribbledom This is also linked from over there: https://old.reddit.com/r/sysadmin/comments/q181fv/looks_like_facebook_is_down/hfda42z/
So funny "There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified."
Very hard to use the network to fix the network when the network is down.
@fribbledom ah. Maybe the age of spybricks is not upon us. If other corporations have their toes mashed by this little hiccup maybe that will all come crashing down.
Nahhhh. It'd have to be way worse than this to do that.
@fribbledom cloudflare has a nice graph showing 30x increase in DNS traffic for the affected domains, but they were able to handle it this time https://blog.cloudflare.com/october-2021-facebook-outage/
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!