Is RevenueCat down?

We’re seeing an increased rate of errors when communicating with Apple’s backend services. This is resulting in some HTTP 522 responses from our receipts endpoint. We’ve enabled mitigations to minimize the impact on RevenueCat customers, and no purchases are currently being blocked as a result. We’ll continue monitoring the issue and update this thread.

Apple has reported that the issue is now resolved, and we’re also seeing error rates return to normal. We’ll keep monitoring.

The issue has been resolved. We’re now making sure that any purchases affected by the outage are reprocessed.

We are currently investigating elevated error rates and latency across multiple of our APIs

We have rolled out a fix and are seeing early signs of improvement.

Error rates and latency have returned back to normal.

We are seeing increased latency on webhook delivery and are working to mitigate

Webhook delivery latency is back down to normal levels.

Webhook delivery latency is still on normal levels and the system is stable. We consider the incident resolved.

We are currently investigating a complete outage affecting Rico. All requests to the service are failing at this time. We will provide an update as soon as we have more information.

We've identified the issue: an outage with one of our upstream AI inference providers is causing Rico to fail. This is an external dependency issue, and we are actively monitoring the provider's status and working on mitigation options. We will post another update as soon as we have more information.

Our upstream AI inference provider has recovered, and Rico is now operating normally. We're continuing to monitor closely to confirm full stability before marking this resolved. We will provide a final update shortly.

Rico continues recovered and stable, we consider the incident resolved.

Developers setting up a newly created app may see "Credentials need attention" for their In App Purchase key. This is caused by Apple's App Store Server API rejecting recently registered Bundle IDs. Existing apps are unaffected, and we have reported it to Apple. Regenerating the key does not resolve it.

We're awaiting a fix from Apple. Apple’s App Store Server API returns a 401 for Bundle IDs registered on or after 24 July. The same key works against older Bundle IDs in the same account, and we have reproduced this directly against Apple’s API. The failure happens before any RevenueCat logic. For affected apps, the “Credentials need attention” warning is not accurate. Your key is almost certainly correct. Regenerating the key, re registering the Bundle ID or recreating the app will not resolve it. We have reported the issue to Apple and will continue to assist Apple in resolving it.

The issue appears to have been resolved on Apple's side. We're seeing keys being correctly validated now.