Update: Oops, I meant TTL.. not ARP :D
The reason being is most users connect to Facebook or Instagram DAILY... which means their TTL cache would still be applied...
This happened either several days ago and users are just now starting to be affected as TTL cache expires... or something more deep. Actual routing problems.
This could be the start of the take down and the 10 days.. I hope all of us are prepared if so.
when the SHTF the people they thought were crazy all of a sudden turn into their saviours
Its not just a DNS issue. Sites are inaccessible via direct ip as well.
Can someone verify?
telegram is down now too
Not for me, but I see it on downdetector as having issues.
telegram is indeed back up for me now
Hard to believe when Q predicted this 3 years ago TO THE DAY.
Allegedly employees couldn't get in because door card readers were also down.
NSA dat u?
No longer alleged, confirmed. At least the card reader thing.
Update: FB routes deleted from global routing tables.
Only FB themselves could do that. Or ICANN...
Not true
Since I'm not emotionally dependent on any social media, it can stay down as far as I'm concerned.
I can still see IG posts from a few hours ago
ARP table doesn't mean anything here. ARP is Layer 2, how you get to your router. From there, IP routing takes over.
Beat me to it.
You are right... ARP caches the mac address. Brain fart.... I mean't TTL... DNS propagation time..
I gotchu... posted a top-level comment with some findings, you got the snarky answer because I was mid-dig and confirming what I was seeing with a few of my peers.
No worries! I want to be corrected when I write something that is incorrect, even if it is a sarcastic or snarky correction
Also, I didn't take your correction as snarky at all :)
We are all G fren
Update: DNS is not the cause, but FB's DNS server is a victim.
TL;DR, Their BGP AS "disappeared" from the Internet. This is extraordinarily rare, so rare that I've never seen it happen on a production network, unless it was a deliberate decision (like consolidating companies under a single AS).
For the normies, BGP routing is like how Verizon knows how to connect a call from your phone to your buddy's phone on AT&T's network. You know your buddy's phone number, but that call isn't going to get through. This is equivalent to Verizon not knowing AT&T even exists.
The BGP "issue" (I'm not saying failure because I don't think it failed) caused their DNS servers to become unreachable from the Internet, and since they run a very small DNS TTL, those IPv4 entries have aged out. What's interesting is that their IPv6 entries are still valid, but they're not native IPv6 end-to-end, so routing still breaks at IPv4-enabled segments.
There were no changes outside of the ordinary to their DNS in the last year. Also no routing changes, and I checked to see if there was a nexus between their networks and the DoD space that migrated out to Florida last year- there isn't. No planned outages scheduled, either.
While a route disappearing from BGP is common, an entire AS is not. BGP poisoning is a standard attack, but it doesn't make an AS "go away". This is more insidious.
My opinion, and not financial advice b/c I'm a retarded crayon eater, if this wasn't a US Government shutdown, it certainly is something in Russia's wheelhouse.. and Zuck pissed off Putin.
Can confirm. Correcting a DNS entry, even with many many security layers, can be done fairly quickly. Propagation has been less than 20 minutes or so for the last few years.
This is odd.
Be still my heart.
I should probably grab additional cash just in case more systems drop.
They basically did this:
https://files.catbox.moe/ew5w30.jpg
They automated their BGP peering and it went awry, completely locking out their datacenters, so people had to be sent in to manually configure the routers.
ARP maps MAC to IP. Layer 2 is out of the mix
This guy networks.
Your instincts serve you well, OP. Who has ability to killswitch/ access to any domain, worldwide? Who really owns the internet? Who invented it? Why?
Now plug in Q drops.
Answer these any let the fog lift.
This is only due to your own cache locally.
do
ipconfig /flushdns
then try
nslookup facebook.com
Why is your comment and post history so... troll-y?