RevenueCat incident: Scheduled Data Exports delayed for GCP

Affected components

• Scheduled Data Exports

1. resolvedApr 10, 2026, 10:42 UTC

   This incident has been resolved.

2. monitoringApr 10, 2026, 10:42 UTC

   The issue affecting Scheduled Data Exports to GCP has been fully resolved. All delayed exports have now been successfully delivered, and export processing is operating normally.

3. monitoringApr 10, 2026, 09:04 UTC

   Fix has been rolled out and we are redelivering exports that were affected.

4. identifiedApr 10, 2026, 08:24 UTC

   We have identified an issue with Scheduled Data Exports. We’re rolling out a fix.

5. investigatingApr 10, 2026, 07:49 UTC

   We have detected some issues causing some delays with Schedule Data Export deliveries to GCP

What APIStatus.watch saw

Our 5-minute checks didn't record a change in RevenueCat's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• Elasticsearch: Connection issue to Kibana via the Cloud UI SSOMajor · Apr 9, 2026, 15:37 UTC
• Elasticsearch: Privatelink hostnames reported by API are incorrectMajor · Apr 9, 2026, 20:46 UTC

How often does RevenueCat have incidents?

RevenueCat reported 10 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 2h 20m. See RevenueCat's uptime and incident history