We have identified an errant deploy which was aiming to add caching to our API. In doing so we missed a calculation and were returning negative numbers. This has been reverted and we've identified improvements in our end to end testing suite to capture this in the future.

As always, we appreciate your patience.