RevenueCat incident

Elevated error rate

Minor Resolved View vendor source →

RevenueCat experienced a minor incident on June 12, 2025 affecting API Uptime, lasting 1h 46m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 12:29 PM UTC
Resolved
Jun 12, 2025, 02:15 PM UTC
Duration
1h 46m
Detected by Pingoru
Jun 12, 2025, 12:29 PM UTC

Affected components

API Uptime

Update timeline

  1. investigating Jun 12, 2025, 12:29 PM UTC

    We are facing issues with our caching infrastructure and are temporarily increasing database capacity to handle the load.

  2. identified Jun 12, 2025, 12:33 PM UTC

    We are facing issues with our caching infrastructure and are temporarily increasing database capacity to handle the load.

  3. identified Jun 12, 2025, 01:08 PM UTC

    We are experiencing elevated latency and error rates. The root cause is that our memcache cluster is doing an undesirable rolling restart, each time a node restarts we’re experiencing momentary elevated latencies and error rates. About half of the nodes have restarted, we’re attempting to mitigate by adding server and database capacity, but once all nodes have restarted things should be smooth. Server to server calls are primarily affected, the SDK has mitigations that should reduce impact to zero.

  4. monitoring Jun 12, 2025, 01:20 PM UTC

    We have been able to stop the memcache servers from restarting and our latency and error rates are trending back to normal. We are continuing to monitor the situation.

  5. resolved Jun 12, 2025, 02:15 PM UTC

    The API has remained stable so we are marking this incident as resolved.