dChan
Anonymous ID: 69fb41 Oct. 4, 2021, 11:26 a.m. No.98366   🗄️.is 🔗kun   >>8377 >>8378

Stolen from /qr/

 

4 carriers & their air wings operating together in waters S.W. of #Okinawa, as waves of #Chinese planes harass #Taiwan - Via @NavyLookout

 

https://twitter.com/indopac_info/status/1445085455368687621

Anonymous ID: 69fb41 Oct. 4, 2021, 11:58 a.m. No.98371   🗄️.is 🔗kun   >>8372

https://www.reddit.com/r/sysadmin/comments/q181fv/looks_like_facebook_is_down/

https://archive.is/mZCq4

 

/u/ramenporn Update 1440 UTC:

 

As many of you know, DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC).

 

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.

 

Part of this is also due to lower staffing in data centers due to pandemic measures.

 

Update from /u/ramenporn

 

No discussion that I'm aware of yet that is considering a threat/attack vector.

 

I believe the original change was 'automatic' (as in configuration done via a web interface). However, now that connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally.

 

Looks like the facebook hitmen got to /u/ramenporn, rip we hardly knew yee.