RevenueCat: Incident updated: Increased API errors

Incident updateNormal progress (rule, 100%)Changed 2026-11-10 00:33 UTCstatus.revenuecat.com

Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what RevenueCat removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1

~~investigating~~

monitoring

AddedUpdatemonitoring2026-11-10 00:24 UTC#2

not present

API is recovered, and we're in contact with our main cloud provider to determine the root cause of what seems like a problem on their end. We'll provide more updates soon.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

History of this incident

TodayTuesday, November 10Tue, Nov 10

2 incident changes

Normal progress
08:03Incident
Incident updateIncreased API errors
Normal progress
00:33Incident
Incident updateIncreased API errorsthis change

Cite this

Incident updated: Increased API errors on RevenueCat’s status page, changed 2026-11-10 00:33 UTC (change 1 of 2).

Title: Incident updated: Increased API errors
Vendor: RevenueCat
Date: 2026-11-10 00:33 UTC
URL: https://rewindex.com/change/ra3ce9ca25a3d23

All RevenueCat changes RevenueCat profile Markdown JSON