Thanks to @JCOSU86 for the kind heads up regarding this morning's database tomfoolery and cheeky shenanigans.
All fixed, I think. The AWS instance farted and then the database burped in response -- I know these highly technical explanations aren't particularly useful to the layman, but transparency is a good thing.
All fixed, I think. The AWS instance farted and then the database burped in response -- I know these highly technical explanations aren't particularly useful to the layman, but transparency is a good thing.