"At around 4:30 AM PST, one of our Availability Zones (mec1-az2) was impacted by objects that struck the data center, creating sparks and fire."

[neurovagrant@masto.deoan.org]

SREs be like, "this was NOT in the fucking manual."

[neurovagrant@masto.deoan.org]

The one time it’s not DNS…

[viss@mastodon.social]

@neurovagrant there was a fucking rad writeup i read once about a bunch of dudes who ran dsl to barracks and had a dslam and everything inna warzone, and dude had to keep running out after mortar fire to repair twisted pair

[tekchip@mastodon.social]

@neurovagrant we don't know what caused the objects to fall/fail on the datacenter. There's still a solid chance DNS was involved. I don't think we can confidently say it was targeted.

[davep@infosec.exchange]

@neurovagrant I'm thinking of my SRE friends in Saudi who I helped troubleshoot their healthcare system a few times (along with my day job of being an architect). Can't be fun for anyone over there.

[johntimaeus@infosec.exchange]

@Viss @neurovagrant

You remember enough to find the article?

Wondering if it was one of my students.

[avuko@infosec.exchange]

@neurovagrant Drone Negated Service

Yeah, I’m going to bed right now. 🫣

[viss@mastodon.social]

@johntimaeus @neurovagrant i just gave it a swing and i found a shitload of call of duty results. ill have another go later

[securitywriter@infosec.exchange]

@neurovagrant This is my eternal argument with SaaS and colo providers.

Is your DC hardened?

“Yes we have SOC2 and a guard at the gate”

That’s not what I meant.

[viss@mastodon.social]

@SecurityWriter @neurovagrant but surely shifting language around via contracts is the solution!

[aakl@infosec.exchange]

@neurovagrant Darn. AI missed.