It's currently running on a single azure appworker, you might've hit it during a service autoheal/reset. There's a fair bit of overhead for every connection since it's designed for our subscribers to use and get realtime stats on their connection, was not expecting to get tens of thousands of hits by linking to it in a hacker news comment.
It's currently running on a single azure appworker, you might've hit it during a service autoheal/reset. There's a fair bit of overhead for every connection since it's designed for our subscribers to use and get realtime stats on their connection, was not expecting to get tens of thousands of hits by linking to it in a hacker news comment.