We had all this conversation two weeks ago when this happened the first time.

There is no reason for it not being massive redundant in AWS or elsewhere, and I was hoping this AM's 'outage' could have been a migration to AWS. Of course, anyone that did that correctly would have done it so the outage was about ten minutes as DNS migrated from whereever to Route53 (AWS DNS). No reason for several hours....
We shall see if anything good comes of it. We never got a good explanation of the first outage except maintenance, and, as I said then, NO one would do maintenance on the weekend of a consumer facing utility like this. Never. Unplanned Maintenance, sure, which means it blew up.