Changes / RevenueCat / Error spike in API
RevenueCat: Major incident: Error spike in API
Summary
RevenueCat reported a major API Uptime incident involving a spike in database-related errors from 2026-01-14 11:00 UTC to 2026-01-14 11:54 UTC, lasting 54 min. Fortress was enabled to mitigate errors, then disabled when the error rate returned to normal at 11:16 UTC; all Fortress receipts were replayed by resolution.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Error spike in API
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-01-14 11:00 UTC
Before: not present
After: 2026-01-14 11:54 UTC
Before: not present
After: API Uptime
Before: not present
After: We have detected a spike in errors related to our database and have enabled Fortress to mitigate while we investigate.
Before: not present
After: We have disabled fortress and the error rate is back to normal. We will be monitoring the systems.
Before: not present
After: All fortress receipts have been replayed.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Error spike in API (this change) RevenueCat reported a major API Uptime incident involving a spike in database-related errors from 2026-01-14 11:00 UTC to 2026-01-14 11:54 UTC, lasting 54 min. Fortress was enabled to mitigate errors, then disabled when the error rate returned to normal at 11:16 UTC; all Fortress receipts were replayed by resolution. | Major incident |
All RevenueCat changes → · RevenueCat profile · Markdown · JSON