I apologize for any inconvenience this may have caused. We take uptime extremely seriously and know that events like this are unacceptable.
A burst of traffic to our API caused our database cluster to max out available memory. This caused an auto-scale event to occur, which then caused the database to become unresponsive, requiring a restart.
After the database came back online, and further investigation, we implemented more specific indexing on the data collections to optimize the inefficient queries.
What we will do to prevent this in the future
We have now implemented optimized indexes on all database queries which were showing inefficiencies.
We will continue to monitor any new query operations that require optimizations.