We're currently investigating elevated error rates and response times with the API. We'll post an update soon.
-
-
On 2019-07-10 UTC, the Stripe API had two periods of severely degraded availability. Our root cause analysis:https://stripe.com/rcas/2019-07-10
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Downtime happens... Is there anything you can share as to how we as devs can provide mitigation when this happens in the future? I assume we could just keep our tokens and then process them at a future time when the service is back online? Any docs / best prac. would be helpful.
-
Strategy around retrying requests will vary depending on your integration and the circumstances of each failed request, but we like the idea of a 'best practices' guide—we'll look into this. In the meantime, please write in if you have any questions: https://support.stripe.com/contact
- 2 more replies
New conversation -
-
-
Are you still planning to provide a post-mortem? Serious downtime plus poor communication doesn't inspire confidence.
-
We'll be sharing a post-mortem shortly on this thread:https://twitter.com/stripestatus/status/1149152970950373377 …
End of conversation
New conversation -
-
-
Please provide an RSS feed for these!
-
Thanks for your feedback—we'll be sure to look into this.
End of conversation
New conversation -
-
-
Could not connect to Stripe (https://api.stripe.com/v1/customers ). support@stripe.com. (Network error [errno 7]: )
-
This is likely unrelated to the incident on July 10, but we'd like to dig into it to find out more. Would you mind sending us an email via https://support.stripe.com/contact with some more details so we can take a look?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.