Companies / RevenueCat / incidents
RevenueCat: AWS Connectivity Issues Causing API Downtime
Timeline of updates
- resolved
Marking resolved. AWS has communicated with us that they've resolved the underlying issue and we don't expect further downtime. What to expect: 1. New purchases could not be processed by RevenueCat during the downtime. If your app uses one of RevenueCat’s SDKs, it will retry sending the purchase to RevenueCat the next time users open the app. 2. Existing purchases that were already in RevenueCat were not affected aside from delayed event generation and dispatch. Those users’ purchases continue to be tracked. 3. If you use our API directly (for example, you use Stripe with RevenueCat or use our API directly from your app without using our SDKs) you should retry any failed requests. 4. Any requests that are retried will cause events to be generated and dispatched to any integrations you have configured in RevenueCat. 5. ETLs, charts, and customer lists are all operational and up to date.
From RevenueCat’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.revenuecat.com (opens in new tab). RevenueCat profile · Recent RevenueCat incidents · Markdown · JSON