Back to overview
CMS unavailable (31/05/2022)
Jun 11 at 07:00pm CEST
Affected services
CMS
API
Resolved
Jun 11 at 07:00pm CEST
On June 12th at 7:00pm CET, we noticed an unusually burst of traffic to our servers causing our database CPU usage to peak to 100%. This resulted in the CMS going down. Immediate action was taken to upscale our database capacity. At 7:25pm CET this migration was completed and it took around 10 more minutes for all queued API traffic to be processed.
We are still investigating the root cause of this unusual traffic spike.
Affected services
CMS
API