Subscription creation timeout
Incident Report for Chargify
From 21:30 UTC to 21:40 UTC we experienced a backup in subscription creation that caused some signups to result in timeout ( HTTP response 502 ). Although your request may have timed-out, the subscriptions were in fact created.

If your API client: 1) Does not use duplicate prevention and 2) blindly retried the request without checking whether the subscription was created, it's possible a duplicate subscription was created for the same customer.
Posted over 2 years ago. Nov 18, 2016 - 15:52 CST