TY BAKER!!!

>>5070290 (lb)

>>5069887 (pb)

>>5069925 (pb)

This is spicy!

WF apparently had a fire in its data centers today, their backups were also taken down.

WF is pretty much the shittiest bank on the planet (and that's saying something!) after Wachovia imploded, WF acquired Wachovia and Wachovia mgmt became WF mgmt (similar to Apple and Next iirc)

Seems like moves are being made against WF…

>>5071104

I am clearly retarded and don't know how formatting works. Thanks for reading.

>>5071167

That's exactly what I'm thinking - seems like a coordinated effort on multiple fronts, but is it them sabotaging themselves to hide evidence? Or white hat fucking them up?

I didn't realize that the LA Ops were even remotely tangentially related to WF, but now almonds are activated.

>>5071210

https://www.reddit.com/r/sysadmin/comments/ao4g2y/wells_fargo_is_down_declining_transactions_and_no/

"Wells Fargo is down. Declining transactions and no access to the web portal."

""Throwaway since I have first hand knowledge. Fire suppression went off in one of their main Data Centres from some utility work this morning. No power to any of the network or compute equipment and some failovers did not work as expected.

Edit: I've gotten a number of DMs asking for updates over the last few hours - so for those interested the last I heard (15-20 min ago) was that everything minus core network gear was manually being unplugged from any PDUs to help the control the initial power-on. No ETA on when that will be finished, let alone when things will be back up."

>>5071341

>>5071210

Didn't remember exactly, all backups aren't fried, but "some failovers did not work as expected" is almost the same.

Thanks for forcing clarification.