Udstedelse med firewall
OutageKritisk hændelse
Berørte komponenter
DashboardAPI
- investigating
Vi undersøger i øjeblikket dette spørgsmål.
- resolved
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
51 Apphud incidents · juni 2024 — official updates, affected components, duration and resolution details.
Vi undersøger i øjeblikket dette spørgsmål.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplever et problem med baggrund job behandling, hvilket resulterer i forsinkelser i analytics og begivenhed data. SDK API 'er påvirkes ikke. Data forventes at indhente realtid inden for ca. 30 minutter. Vi undskylder ulejligheden.
Et fix er blevet gennemført, og vi overvåger resultaterne.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
We are currently investigating this issue. There is problem at our data center. We are in close touch with cloud provider. Our engineers our trying to do their best to solve the issue ASAP
We are continuing to investigate this issue.
A fix has been implemented by our Cloud Provider and we are monitoring the results.
This incident has been resolved. Cloud Provider has fixed the issue.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
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.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
This incident has been resolved.
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 40 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.
This incident has been resolved.
Due to a bug introduced during recent maintenance, experiments that were in a Running state as of January 19 until January 21 17:45 UTC were unintentionally paused. The issue has been fixed, and all affected experiments have been unpaused and are running normally. Data for the affected period may be incomplete. No action is required. We are sorry for the inconvenience.
Due to a recent platform upgrade, the iOS mobile app is temporarily not functioning. An updated version will be released to the App Store, and users will need to update to the latest version. We’ll notify you when the update is available.
The updated app version in now available in the App Store: https://apps.apple.com/us/app/apphud-the-official-app/id1587154106
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We experience partial API issues caused by major Cloudflare outage: https://www.cloudflarestatus.com/
Update: SDK seems to be working without any disruptions, since it's not using Cloudflare. Only Apphud dashboard is not accessible in certain countries
We are continuing to investigate this issue.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently experiencing delays in background job processing, which is affecting the following services: * Event delivery to integrations * S2S event webhooks The current delay is approximately 1.5 hours. 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.
This incident has been resolved.