caterpillarcowboy: mcdavis: Tumblr Uptime (http://tumblruptime.icodeforlove.com/) This page provides you with Tumblr’s current API status. The API method’s are checked every 15 minutes for valid responses, and are benchmarked. It’s interesting to see some benchmarks in a visual way after spending time with Tumblr’s API.  Both the /api/delete and /api/read methods, according to this, have a 15% uptime.  Meaning if you’re relying on this API for anything you build, your tool will likely only work 15% of the times it is loaded.  And that’s not even touching the high latency you’ll come across working with it. Between a 15% uptime, a terribly slow response and a bunch of missing features, is it any wonder that we’re not seeing any real innovation on the Tumblr API? Note: data is only from the last 24 hours. Not that it makes things OK. When most companies talk about many 9s of uptime they have (99%, 99.9%, 99.999%), here we have 15%. Awful. This has definitely been a problem for me lately.  I run a small side-project called trntbl that lets you listen to Tumblr-powered playlists.  Unfortunately, for the better part of the last week it has been down as its operation is tied to the Tumblr API, and this has resulted in quite a few angry users who are blaming me.  Don’t get me wrong, I love Tumblr and appreciate all of the amazing things that they provide us for free, but at this point I am seriously reconsidering how much time I want to invest into something so unreliable.

caterpillarcowboy:

mcdavis:

Tumblr Uptime (http://tumblruptime.icodeforlove.com/)

This page provides you with Tumblr’s current API status. The API method’s are checked every 15 minutes for valid responses, and are benchmarked.

It’s interesting to see some benchmarks in a visual way after spending time with Tumblr’s API.  Both the /api/delete and /api/read methods, according to this, have a 15% uptime.  Meaning if you’re relying on this API for anything you build, your tool will likely only work 15% of the times it is loaded.  And that’s not even touching the high latency you’ll come across working with it.

Between a 15% uptime, a terribly slow response and a bunch of missing features, is it any wonder that we’re not seeing any real innovation on the Tumblr API?

Note: data is only from the last 24 hours. Not that it makes things OK. When most companies talk about many 9s of uptime they have (99%, 99.9%, 99.999%), here we have 15%. Awful.

This has definitely been a problem for me lately.  I run a small side-project called trntbl that lets you listen to Tumblr-powered playlists.  Unfortunately, for the better part of the last week it has been down as its operation is tied to the Tumblr API, and this has resulted in quite a few angry users who are blaming me.  Don’t get me wrong, I love Tumblr and appreciate all of the amazing things that they provide us for free, but at this point I am seriously reconsidering how much time I want to invest into something so unreliable.

(via mikehudack)