4 ms·

This seems to be caused by a software bug (at least, I'd hope so). The site continues to make requests on a loop, driving up data and resource usage.