RevenueCat Status

Resolved: The incident has been resolved.

Monitoring: A fix has been implemented and rate-limit errors are back to baseline. We will continue to monitor.

Identified: At 18:27 UTC we noticed an increase in rate-limit errors from our v2 API endpoints for some developers since ~14:00 UTC.

We have identified the issue and are implementing a fix.

Resolved: The underlying infrastructure issue has been addressed, and RevenueCat services are now operating normally again.

Temporary mitigations have been removed as full service has been restored.

We are continuing to monitor the system closely to ensure stability.

Investigating: We are currently experiencing an incident affecting parts of RevenueCat’s web infrastructure. To reduce impact for customers and their users, mitigations have been activated:

What should continue to work normally: apps should continue to load paywalls using cached product data, users should still be able to complete purchases, and users who purchase during this period should continue to receive access to the content or features they bought

What will not work normally during this incident: some real-time and customization features may be degraded while Fortress is active. This includes Offering experiments and customer-specific Offering customization, which may not be applied during the incident. Webhooks and some third-party integration events may also be delayed rather than delivered in real time

What happens after recovery: once normal service is restored, we will replay queued requests so purchase records, entitlement confirmation, webhooks, and downstream events can be reconciled

We are actively working to restore full service and will continue to share updates as we make progress

Investigating: We have noticed a degradation of service and are investigating the issue.