Tim Beyers

So let's talk about this.

AWS going dark again.

This has happened many times.

Here's what we know.

AWS, like you said, Dave, went offline around 3 a.m.

Eastern time for what appears to have been a couple of hours.

The rolling effects could continue, and we are recording this on a platform called Riverside.

And as soon as I logged in, we got a nice little notice from Riverside saying, hey, AWS went down and services may be affected.

I'm paraphrasing there.

So lots of companies have been affected here.

At issue were some errors in the company's DynamoDB database.

So let me just briefly explain what this is.

Amazon's primary database is DynamoDB.

It's a transactional database.

And it's most famous for being the homegrown Amazon database that they use really to process transactions.

So this is meant to be a highly resilient, highly replicated database throughout the Amazon and the Amazon Web Services ecosystem.

This is what they've built their business on.

And what it was subject to, we don't know if it was an attack or just an

error, it was subject to an outage in the DNS system, the domain name server system.

When that happens, when the DNS goes out, and you probably have heard of this, a distributed denial of service attack, that's meant to attack the DNS.