Changes / RevenueCat / Degradation of service
RevenueCat: Critical incident: Degradation of service
Summary
RevenueCat reported a critical degradation affecting parts of its web infrastructure and API Uptime, starting 2026-04-18 20:42 UTC and resolved at 2026-04-18 21:10 UTC (28 min). Mitigations were activated; cached paywalls, purchases and content access were expected to continue working. RevenueCat addressed the underlying infrastructure issue and removed mitigations after restoring service.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Degradation of service
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-04-18 20:42 UTC
Before: not present
After: 2026-04-18 21:10 UTC
Before: not present
After: API Uptime
Before: not present
After: We have noticed a degradation of service and are investigating the issue.
Before: not present
After: 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
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Degradation of service (this change) RevenueCat reported a critical degradation affecting parts of its web infrastructure and API Uptime, starting 2026-04-18 20:42 UTC and resolved at 2026-04-18 21:10 UTC (28 min). Mitigations were activated; cached paywalls, purchases and content access were expected to continue working. RevenueCat addressed the underlying infrastructure issue and removed mitigations after restoring service. | Major incident |
All RevenueCat changes → · RevenueCat profile · Markdown · JSON