Live / RevenueCat / Incident
RevenueCat: Increased API errors
RevenueCat · revenuecat.comMinor incidentResolved2026-11-10 08:01 UTC
Public — what happened
Summary
RevenueCat reported a minor incident involving a higher-than-normal number of errors from its API, which began at 00:13 UTC on November 10, 2026. About eleven minutes later, at 00:24 UTC, the company said the API had recovered and that it was working with its main cloud provider to find the root cause, which it said appeared to be a problem on the provider's side. RevenueCat marked the incident resolved at 08:01 UTC the same day.
Affected
API Uptime
Timeline
- Started — 2026-11-10 00:13 UTC
- Investigating — 2026-11-10 00:13 UTC
- Monitoring — 2026-11-10 00:24 UTC
- Resolved — 2026-11-10 08:01 UTC · 7h 48m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach RevenueCat against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for RevenueCat: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the RevenueCat report →
More from RevenueCat
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.