Tuesday, July 2, 10:54 - 15:57 UTC
Some customers received erroneous messages stating they were running at their maximum concurrency, preventing them from starting new tests.
During a routine deployment, a serialization library was updated. The update contained a dependency with a non-compatible, breaking change that made the read/write values of this service to not work.
The deployment was rolled back.
We have deployed an upgrade which removed the dependency on the library that caused this issue. We will also be improving our post release external monitoring system to monitor the API endpoint that was affected by this issue.