We were able to pinpoint the recent downtime to a faulty Redis instance from a third party provider (we use Redis for queuing jobs like publishing and syncing). To avoid any further interruptions, we have migrated our Redis servers to AWS in a high availability (multi-AZ) configuration. This redundancy will help avoid a single point of failure, and should make the service more stable overall. Thanks again for your patience while we sorted this out.
As always, you can reach out to firstname.lastname@example.org with any questions.