A status page is critical for public API programs. If people depend on your API, you owe them transparency. That’s why we find Twitter’s status page so interesting. Besides the hilarious bug.
This is Twitter’s. It is clean and straightforward enough. With that said, there is a problem. Is this anything more than a ping test? I see uptime and metrics, but functionally speaking is this validating the payload in detail? I doubt it. Which is fine, but what happens where there is a hiccup. What do you know besides the dot turns red?
That’s the benefit of a API Fortress. We start at the regression tests, and that can be used to power your own status page. If there is an issue, we have detailed reports to tell you what happened.
Seems simple enough, but the reality is that pages like this are the norm. Statuspage.io customers usually update it manually, which means the reporting is not real-time, not does it have much detail until someone decides to post what is happening.
So now for the best bug of the week. Apparently the page is powered by Nimsoft Cloud Monitoring. Nimsoft was acquired by CA it seems, as the link now directs users to this page at CA. There is another link in the footer, a link to Nimsoft’s Twitter account @nimsoft. Well, since being acquired, CA seems to have abandoned control of that handle. What does this all mean?
This is the official Twitter of the company that powers the Twitter status page. The bio is the best part. “Getting a Break at Tweeting because i’m Generating $450 a day employed via the internet from my house. My best ambitions inevitably came perfect.”
Ladies and gentleman, we at API Fortress would like to guarantee that we will never abandon you to make $450/day from our homes.
Take your status pages seriously. Give your customers more than a red or green dot, but provide them with some real-time detail into what is happening. Finally, if your platform is having issues because your team is off making upwards of $450/day, keep that a secret.