60 Revenuecat incidents · 2025年7月 — official updates, affected components, duration and resolution details.
与苹果公司后端服务沟通时, 这使得HTTP 522从我们的收货端点得到一些响应. 我们已让减税措施尽可能减少对InformCat客户的影响, 我们将继续关注此事.
苹果公司报告说, 这个问题现在已经解决了, 我们将继续监控.
这个问题已经得到解决。 目前我们正确保受停产影响的任何采购都经过重新处理.
自动翻译自官方事件更新。
We are currently investigating elevated error rates and latency across multiple of our APIs
We have rolled out a fix and are seeing early signs of improvement.
Error rates and latency have returned back to normal.
我们看到在提供网页浏览器方面越来越不耐烦,并正在努力减少
Webhook delivery latency is back down to normal levels.
Webhook delivery latency is still on normal levels and the system is stable. We consider the incident resolved.
自动翻译自官方事件更新。
We are currently investigating a complete outage affecting Rico. All requests to the service are failing at this time. We will provide an update as soon as we have more information.
We've identified the issue: an outage with one of our upstream AI inference providers is causing Rico to fail. This is an external dependency issue, and we are actively monitoring the provider's status and working on mitigation options. We will post another update as soon as we have more information.
Our upstream AI inference provider has recovered, and Rico is now operating normally. We're continuing to monitor closely to confirm full stability before marking this resolved. We will provide a final update shortly.
Rico continues recovered and stable, we consider the incident resolved.
设置新创建的app的开发者可能会看到他们In App Push键的"证书需要注意". 这是由于苹果公司的App Store Server API拒绝最近注册的 Bundle IDs. 现有的应用程序没有受到影响,我们已经向苹果公司报告。 重生键不能解决它.
我们正在等待苹果的修复。 苹果公司的App Store Server API 返回了在7月24日或之后注册的Bundle IDs的401个. 同一键对同一账户中的更古老的 Bundle IDs 有用,我们直接在苹果公司的API 上转载了这一点. 失败发生在任何FANSCAT逻辑之前. 对于受影响的应用程序,“需要注意的证书”警告并不准确。 你的钥匙几乎完全正确 重新生成密钥, 重新注册 Bundle ID 或重新创建应用程序不会解决它 。 我们已经向苹果公司报告了这个问题,并将继续协助苹果公司解决这个问题.
这个问题似乎已经在苹果方面解决了. 我们现在看到钥匙被正确验证了.
自动翻译自官方事件更新。
我们正在调查苹果公司服务的错误 我们建立了一个临时的后退机制,应提供有限的功能.
苹果公司承认多种服务存在问题. 在问题得到解决之前,我们将继续发放短期的临时津贴。 一旦出错率恢复正常,我们将禁用这种缓解措施并重新确认受影响的采购.
我们正在监视接收服务器进行回收 因为我们无法与商店验证新购买,所以给予新用户短期权益(最多24小时). 防止客户在特殊情况下被拒绝访问,例如部分应用程序商店停放 连接恢复后,如果验证成功,预计会定期进行初始购买. 如果验证失败,临时应享权利将到期
Apple 接收服务器已备份 我们在重放购买 临时应享待遇要么变为“实际”购买,要么到期,在停用期间的相关网络购物和互动活动将开始通过
我们正在继续重播受影响的收据。 这并不影响在停业窗口期间进行采购的客户,因为税务委员会给予的临时应享权利将确保无缝过渡。 一旦所有采购都重新播放,这一事件将被关闭.
所有受影响的采购都已重新播放.
自动翻译自官方事件更新。
我们得到5xx错误 当呼叫 Apple Store Kit 2 验证收据。 我们已经使缓解措施能够不间断地购买客户,我们正在调查这一问题.
自动翻译自官方事件更新。
App Store Connect正在经历缓慢的响应时间,这可能会影响一些用户. 在管理仪表板上的或通过MCP的App Store产品时,它们可能会遇到延误或问题.
App Store Connect正在经历缓慢的响应时间,这可能会影响一些用户. 在管理仪表板上的或通过MCP的App Store产品时,它们可能会遇到延误或问题.
App Store Connection 问题现已解决.
自动翻译自官方事件更新。
FinanceCat app的花旗市场页面不再显示安装按钮,以在花旗账户中安装. 这使得无法从"市场"页面在新账上安装"FinancialCat"app. 没有影响现有的条纹连接 。 只有在目前通过Frede cli使用新的Frede Projects集成后,才能将新的Frede 账户连接到FractionCat. 我们正与Frede合作恢复市场页面中的安装CTA按钮,允许不愿使用Frede Cli的客户将Frede连接到他们的FinancialCat账户. 如果您的Frade 账户与 FinanceCat 有问题, 请联系支持 .
这个问题已经通过"Frede"解决了,现在可以通过"Frede Marketplace"页面再次安装"FormCat""Frede"app".
自动翻译自官方事件更新。
SSO的登录和会话表现下降 使用单一签章的客户可能难以在税务卫星仪表板上签字或中断其现有的会议。 这个问题仅会影响到有特别安全安排的组织。 税收中心SDK、购买、订阅、应享权利、API、分析以及数据出口不受影响。 造成这一问题的原因是我们的SSO供应商的性能下降。 我们正在监测局势,一旦掌握了更多信息,我们将再次提供最新情况。 目前无需客户采取行动.
我们的SSO供应商已经查明了错误率高的原因,并实施了固定。 随着服务恢复,注册和会话错误正在减少。 一些使用Single Sign-On的客户可能仍然会遇到间歇性困难,难以签入FinancialCat仪表板,或可能中断他们现有的会议。 这一问题仍限于有特别安全安排的组织。 我们正在继续监测复苏情况,并将在问题完全解决后再提供最新情况。 无需客户采取行动.
这一事件已经得到解决.
自动翻译自官方事件更新。
We noticed that over the last hour, Google has been delaying expected subscription renewals and instead extending the expiration dates of the previously active subscription periods. As a result, RevenueCat is observing a reduced rate of renewal, cancellation, expiration, and billing issue events. We are currently investigating this unusual behavior.
The issue appears to have been resolved on Google's side. Event rates are returning to normal levels. We'll continue monitoring the situation.
This incident has been resolved.
We are getting 5xx errors when calling Apple Store Kit 2 to validate receipts. We have enabled mitigations to keep customer purchases uninterrupted and we are investigating the issue.
We have stopped getting errors from Apple Store Kit 2 and the service is operational. We will continue monitoring all the systems.
This incident has been resolved.
App Store Connect is experiencing an outage that affects some users. Our users may experience issues when handling their app store products on the dashboard or on MCP.
App Store Connect is experiencing degraded performance. Our users may experience issues when handling their app store products on the dashboard or on MCP. This does not impact purchases.
App Store Connect issues are now resolved.
Conversions in the Paywalls Charts are currently not being attributed. We've identified the issue and are working to resolve it. We'll keep this incident open until the issue has been fixed & data has been corrected.
We have deployed a fix for this issue and are currently backfilling the affected data. New conversions are being attributed correctly. We will continue monitoring the backfill process.
This incident has been resolved.
We're observing delays in our background Apple receipt-refresh processing, which may cause some subscription statuses to update later than usual. New purchases, webhooks, and API requests are processing normally. Our team is working on it.
This incident has been resolved.
Our AI assistant Rico is currently unavailable. We are investigating.
We are continuing to investigate this issue.
The outage was caused by an underlying service provider issue, which seems to have been resolved. We are monitoring the situation.
This incident has been resolved.
We are currently investigating an issue affecting automatic translations in the Paywall editor. Customers may be unable to generate new paywall translations from the dashboard. Existing paywall translations are not affected. We have identified the likely cause as a breaking change in one of our translation provider dependencies and are working on updating our integration.
This incident has been resolved. Automatic translations in the Paywall editor are working again. Customers should now be able to generate new paywall translations from the dashboard as expected.
We are observing elevated error rates from the Google Play API. This might prevent some user's entitlements from being granted after purchase. We're working on a mitigation to unlock these customers.
Google Play API started returning some new, undocumented error responses for a subset of subscriptions over the last few hours. Our investigation revealed that the vast majority of them are associated with purchases that expired a long time ago. This means that no new purchases are being blocked, but API requests were still impacted by these unexpected errors. We have implemented suppression for these errors when we can programmatically confirm that they refer to long-expired purchases. This has reduced the errors returned by the RevenueCat receipts endpoint by almost 100%, so the issue is now mitigated. We have informed Google about these new unexpected errors and expect them to work on a permanent fix.
Our mitigations have eliminated the impact on RevenueCat clients. We will continue tracking the situation and following up with Google on a permanent fix.
We are experiencing an increased error rate when fetching subscriber information coming from an incorrect cache. We are currently working on a fix.
A fix has been implemented and error rate is going down. We'll keep monitoring.
This incident has been resolved.
We're investigating an issue where charts v3 data is delayed
We identified and resolved the issue. Charts v3 data is now up-to-date.