Apphud had 45 outages in the last 2 years totaling 185h 28m of downtime — averaging 1.8 incidents per month.
There were 45 Apphud outages since June 17, 2024 totaling 185h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
We've received reports that the Subscribers Retention chart is currently unavailable. Our engineers are actively working on a fix. In the meantime, please use the Net Revenue Retention chart as an alternative. We apologize for the inconvenience and appreciate your patience.
This incident has been resolved.
We are monitoring an elevated number of 502 errors in our backend system. Our engineers are actively investigating the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We experienced an API availability issue from 10:15 UTC to approximately 11:00 UTC due to an unexpected Redis overload caused by recent code changes. Our engineering team identified and fixed the issue on the backend, restoring full functionality to Apphud. We are currently replaying all SDK requests to recover most subscription data. We apologize for the inconvenience and appreciate your patience.
We experienced an issue with Apple Search Ads attribution data starting on February 14, where all attribution data was missing. As a result, dependent integrations, including Asapty and SplitMetrics, did not receive events from our system. The issue has now been resolved, and we will replay all requests from previous days to resend events to the affected integrations. However, due to token expiration, approximately half of the installs recorded on February 14 will be permanently lost. We sincerely apologize for the inconvenience and appreciate your understanding.
We have identified an issue causing delays in processing App Store server notifications for some apps. The delay was due to an issue with one of our background queue processing. As a result, you may notice batched renewal events appearing in the Events table as the system catches up. The issue has been identified and data is currently being processed. We expect normal processing to resume shortly. We apologize for any inconvenience and appreciate your patience.
We experienced a partial delay in analytics data processing. The issue has been identified and resolved, and all systems are now fully operational. No data was lost, and the delayed data has been successfully processed. We apologize for any inconvenience caused and thank you for your patience.
We are currently experiencing delays in data visibility for running A/B experiments. Our team has identified the issue and is actively working on a resolution. We expect the issue to be fixed shortly, and we will provide updates as progress continues. Thank you for your patience and understanding.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Due to server maintenance by our hosting provider, web-to-app links were unavailable on Dec 5, 2024 from 5:00 UTC to 8:50 UTC. We apologize for inconvenience.
We are currently investigating this issue.
We are currently experiencing an issue with our analytics servers due to urgent maintenance conducted by our hosting provider. Rest assured, no data has been lost, and the SDK API is functioning as expected. All analytics data will be fully restored shortly. We sincerely apologize for any inconvenience caused and appreciate your patience.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing an issue where a some portion of requests are returning 500 errors. The root cause has been identified as an urgent maintenance work by our hosting provider. Fortunately, our SDK and backend systems are designed to retry failed requests, so that app users should not experience significant disruptions. The issue is related to a small portion of our servers and is expected to resolve shortly. We apologize for any inconvenience and appreciate your patience as we monitor the situation.
This incident has been resolved.
We've received reports indicating discrepancies in the "Billing Issues" metric for Android apps within the Free Trials Performance report. Our team is actively investigating the root cause of this issue.
This incident has been resolved.
We have identified an issue with the Active Subscriptions chart, which is currently displaying lower numbers than expected. This mostly affects apps with weekly subscriptions. The root cause has been identified, and our engineering team is actively working on a fix to resolve the issue.
It seems like Apple is having global outage with the App Store, which results in failures with the In-App Purchases and receipt validation. We are monitoring the situation.
This incident has been resolved.
Cohorts Tab which inlcudes Subscribers Retention and Subscribers Net Revenue Retention charts was showing empty page. The issue is fixed now.
We've encountered an issue where some API requests are returning a 500 status code. However, the SDK is successfully retrying them. Our team is actively investigating the cause.
We are continuing to investigate this issue.
This incident has been resolved.
We encountered an issue that started at 10:30 UTC and lasted for about two hours. During this time, "Trial Started" events in Apphud were incorrectly recorded as "Intro Started" events. This problem only affected iOS apps using the V1 API (those that haven't uploaded their In-App Purchase Key). The issue occurred because the receipt data from Apple had both the "is_trial_period" and "is_in_intro_offer_period" fields set to "true," which caused a bug on our side. We have added a workaround, and the issue has been fixed. We apologize for the inconvenience caused.
This incident has been resolved.
We encountered an issue that started at 10:30 UTC and lasted for about two hours. During this time, "Trial Started" events in Apphud were incorrectly recorded as "Intro Started" events. This problem only affected iOS apps using the V1 API \(those that haven't uploaded their In-App Purchase Key\). The issue occurred because the receipt data from Apple had both the "`is_trial_period`" and "`is_in_intro_offer_period`" fields set to "`true`," which caused a bug on our side. We have added a workaround, and the issue has been fixed. We apologize for the inconvenience caused.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We recently experienced an outage due to an abnormally high load on our database. Our engineers investigated the issue and identified the root cause at the data center site \(abnormally high rate of TCP Retransmissions\). Following a workaround to the backend code, the issue has been resolved. Our team is currently working on replaying all failed API requests to minimize the impact on affected apps. We apologize for any inconvenience this may have caused and appreciate your understanding. Sincerely, Apphud Team
We have identified an issue where the App Store is failing to respond to the /verifyReceipt endpoint, causing Apphud to be unable to verify some iOS purchases. The root cause is on Apple's side, and we hope it will be resolved soon. Our retry mechanism had been successfully bypassing the issue.
This incident has been resolved.
We are currently experiencing inconsistent analytics data due to an infrastructure issue causing delays in processing some of your data to the analytics service. This results in discrepancies in charts and dashboard, which may vary by up to 5%. Our engineers are actively working on a solution. We apologize for the inconvenience.
This incident has been resolved.
On June 17, between 4 PM UTC and 4 AM UTC, there was a delay in sending events to integrations, varying from 1 hour to 6 hours per individual event. The issue has since been fixed, and all events are now being sent in real-time.