No components marked as affected
Resolved
We've seen no issues since updating the secondary database so we're going to count this incident as resolved.
Monitoring
There was a transient problem with our main database around this time that put a lot of load onto a secondary database cluster that was under-provisioned. The problem corrected itself within 5-10 minutes, but we have increased the resources available to the secondary cluster in case the under-provisioning exacerbated the issue.