Companies / RevenueCat / incidents
RevenueCat: SSL Certificate Issues
Timeline of updates
- resolved
It appears that everything is back to normal. Simple quick and dirty post-mortem: 1. Jacob was getting the renewal emails and he was off this week so didn't see the final emails. We're moving the admin accounts to a shared alias. 2. We need to create better alerts for when throughput drops. We weren't aware of the issue until users contacted us. We should have caught it immediately, but it took us 40 minutes to resolve. 3. We've moved the certificate renewal to a DNS record based approach, which will be much more reliable than one based on emailing the CEO while they are on vacation.
From RevenueCat’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.revenuecat.com (opens in new tab). RevenueCat profile · Recent RevenueCat incidents · Markdown · JSON