Show HN: Monitor the Downtime of 170+ Popular Web APIs
zapier.com
zapier.com
I'll watch this thread all day and answer questions, as well as field requests. This is for you guys, so if we're missing something vital, let us know and we'll get on it.
A couple of things I found to be of value in my project that you might find helpful:
1) Endpoint-level granularity
A lof of APIs are RESTful these days, and the trend is for more to be that way than not. It would be nice to see (optionally) the uptime broken out by resource for that API. APIs generally connect to a bunch of different backend services on the API provider's side (think the difference between SMS and Voice with Twilio), and there's a high likelihood that one part could be down while the other is not (e.g. SMS is down for Twilio, but Voice is not).
2) Response Times
This is tricky because response times can be fickle for any number of reasons like network issues, for example. However, I've found that there is value in monitoring response times and big jumps (e.g. anything 1-2 standard deviations off the norm warrants an alert). What would be really cool is if you can monitor response times across various AWS regions.
1) Some less popular endpoints have lower volume, so that would be a challenge to be sure of issues. However, we could probably aggregate the endpoints that are causing issues and attach them to the report. We'll look into that.
2) Response times are definitely of interest too, we don't track that now though. We'll think on that as well.
https://sandbox.microco.sm/api/debug/slow?method=GET
The data on it isn't accurate at the moment as I keep runnning tests designed to flush caches and then re-request resources which skews the numbers.
I want this kind of data so that if I were a developer implementing against an API I would have real data to tell me what the expected response times for a HTTP method and endpoint.
When we get to producing an uptime page, I was thinking of treating uptime as a relative quality measure rather than a yes|no thing... if an endpoint responds in more than a couple of seconds then it's score might by 80%, and less than 50ms then it's 100%, and unresponsive or down would be 0%.
Question is: Is this kind of thing useful? Does anyone have a preferred format for this kind of data?
Otherwise, looks good.
Screenshot: https://dl.dropboxusercontent.com/u/49805/Status%20%C2%B7%20... (Scroll down to bottom area to see worst of it, like the title "How does this work?".)
Specifically: Amazon Product Advertising API https://affiliate-program.amazon.com/gp/advertising/api/deta...
One cool tidbit about the status board is we automatically track global apps added via our developer platform! https://zapier.com/developer/
We've even had folks add APIs for products they don't own simply because they really wanted to use an certain service with Zapier.
Keep up the good work!!
When I showed this to a coworker, he pointed out http://api-status.com/
Only thing I could suggest would making the headers sticky/fixed since there are so many rows.
Edit: done, should be deployed later today.
There's plenty of limitations, I got rid of it eventually.