Yeah the status page is just checking if the index responds with 200 or at all. I could check specific paths but I cache most of it.
The reason why it behaves like this is because my instances gets hammered with 5 times the usual traffic for almost the last 72 hours.
Looks like legitimate traffic.
I would have to add more twitter accounts as the current number always sits limited at 95-98% which gives you the "rate limited" error message. If you refresh a few times you may get through to a valid session.
I will have to monitor this for the next few days. Adding more twitter accounts is very tedious.
Thanks for voicing your concerns!