Cpu Utilization spiked to near saturation potentially leading to incident with higher db response times

Last update from Tonal

Our care admin tool has a leak where in if someone puts in a 0 it leads to a massive table scan on the backend database. Immediate resolution was switching read endpoints from write to read db. Long term: backend team would consider adding an Elastic Search instance to our stack to support search through our user_profile, devices, subscriber and subscription models.

Read the full incident on the official Tonal status page

Other Tonal incidents

1. 14 Sept 2022, 13:01 UTC

   Elevated API Errors due to a networking issue

2. 5 Sept 2019, 21:31 UTC

   This is an example incident

All recorded Tonal incidents