| Thanks for the honest feedback. Also, what is up with all of that downtime? I think I'd expect my payment provider to have better uptime. Makes me wonder how quality the backend really is. While all downtime is bad, we think 99.99% is decent. The best service providers -- including the services that might power your site -- tend to have guarantees in this range. Amazon EC2 and Google App Engine both have SLAs for 99.95% uptime. More generally, this is part of the point: other payments companies don't tend to talk about their availability at all. We think that this is harmful. What should count as acceptable uptime performance is a fair question. As a first step, we think we should all make our uptime public. Is it just me, or is this really confusing? Which services are responsible for taking payments? If the website goes down, does that affect taking payments? Isn't stripe.js part of the API? If the API goes down, doesn't that affect stripe.js? No, the Stripe site going down won't impact your ability to accept payments at all. stripe.js is optional, and so we've exposed its uptime separately too. Again, other services like Amazon and Google break out their availability on a per-service basis, and I think this makes a lot of sense. |
2. (On the site) please explain what each status is and how they relate (or link to rel docs). I understand the website uses the API; yet sometimes the API is down but not the website...
BTW: I humoured some severe criticism of my business once; it was only years later that I realized how accurate, helpful and crucial it was.