Apphud Outage History

We experienced an issue where App Store Server Notifications and Google Play Real-Time Developer Notifications were not being delivered to Apphud servers. As a result, some subscription events such as renewals, cancellations, or billing issues may not have been processed in real time. The issue has now been identified and fixed. We will replay all missed server notifications and process them accordingly. Subscription renewals and other events will be updated based on their original effective timestamps (for example, renewal or expiry time), so historical data and analytics will remain accurate.

We are currently investigating this issue.

We received reports that some A/B experiment analytics metrics were displaying incorrect values (extremely high or extremely low). Our team investigated the issue and identified the root cause. The fix has been deployed. All A/B test metrics are now displaying correctly and operating as expected.

We received reports about increased response times for SDK API calls, specifically affecting paywalls and placements fetching. The issue has been identified and a fix has already been deployed. We are actively monitoring the system to ensure stability and normal performance levels. We apologize for the inconvenience and will provide updates if necessary.

We are currently experiencing delays in background job processing, which is affecting the following services: * Event delivery to integrations * S2S event webhooks * CSV and ETL exports The current delay is approximately 15 minutes. Our engineering team is actively working to resolve the issue, and all data will catch up to real-time shortly. We apologize for the inconvenience and appreciate your patience.

We’ve received reports that A/B test analytics were displaying 0 trials, even though trials were actually recorded. Our team is currently investigating the issue. In the meantime, refreshing the page should resolve the problem and display the correct data. We’ll provide an update once the issue is fully resolved.

We are currently investigating this issue.