Resolved
Jun 04, 2024 at 07:07pm UTC
On June 4th at 8:15pm, we noticed an unusually burst of traffic to our servers causing our database CPU usage to peak to 100%. At 8:23pm this resulted in the CMS going down. At 8:37pm our database scaling kicked in and services started recovering.