Hasn't hit their status page yet, but our error rates are spiked up again, and they just posted a tweet -> <a href="https://status.stripe.com/" rel="nofollow">https://status.stripe.com/</a><p>5:35 Eastern -> Their status page has been updated
Stripe gets the front page because they are popular with developers, but I've dealt with so many other more-corporate payment processors that are absolutely <i>awful</i> for reliability. Rampant downtime, terrible support, terrible concurrency limits, failure to meet SLAs, terrible documentation (900 page specs that are impossible to read). They all think they are awesome, and yet can't go more than 48 hours without having some system degradation email sent out. I don't want to name them, but they are some of the worst businesses I've ever dealt with. They just want to sit there and collect huge amounts of money for helping you connect to Visa/Mastercard/etc, and do little else.<p>Rage. Stripe hitting a little downtime is nothing in comparison.
We're seeing a spike in error rates and we're working on a fix now. (We've updated our status page: <a href="https://twitter.com/stripestatus/status/1149065544399609856" rel="nofollow">https://twitter.com/stripestatus/status/1149065544399609856</a>)
Kind of incredible that this is the first time I remember Stripe being down in a long, long time.<p>Serious kudos to their team and hope they get this resolved soon :)
It would be great if Stripe would offer an RSS feed for status updates in addition to twitter posts. A lot of other services have one and it's very convenient to subscribe to in Slack for updates. At my current company, for example, we have a #third-party-outages channel which we have all available third party services (GitHub, NPM, CircleCI, Slack [yes, it's meta], HackerOne, etc.) status page RSS feed notify in case of an outage.
Ran into this one in the wild when it happened, before stripe status had even tweeted about it. I was trying to order doordash and got a "Could not deserialize JSON object" error when adding a credit card. Hope this is fixed soon, the girlfriend and I are very hungry :(<p>Edit: update if anyone cared, API seems back up and we have ordered food! :)
The thread from earlier today is <a href="https://news.ycombinator.com/item?id=20403774" rel="nofollow">https://news.ycombinator.com/item?id=20403774</a>.
The last error message on their credit cards endpoint reads «This API method has been temporarily disabled due to exceptionally high traffic». It might be a DDoS attack.
Is it due to another Fiber Cut somewhere? Recently almost the entire east coast was down due to fiber damage. I guess the cloud services are as good as the wires that run in the ground.
Second time today. This has been a painful day. That uptime percentage is really ticking down fast. The developer/test mode APIs also seem to be down now as well.
Anyone have any good advice on storing a failed transaction and retrying later?<p>Is that even feasible with Stripe?<p>Obviously there would be security considerations.