Störungsverlauf von Appsflyer

1. 16. Oktober 2026 um 05:50 UTCidentified

   Wir untersuchen ein Problem, das sich auf die Verfügbarkeit des Protect360-Dashboards auswirkt. Wir werden ein Update bereitstellen, sobald weitere Informationen verfügbar sind.

2. 16. Oktober 2026 um 06:54 UTCresolved

   Die Verfügbarkeit des Protect360-Dashboards wurde wiederhergestellt. Unsere Teams überwachen weiterhin die Leistung. Wenn Sie weitere Probleme haben, wenden Sie sich bitte an den technischen Support.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. Juli 2026 um 15:08 UTCinvestigating

   Möglicherweise treten Probleme mit dem Login und/oder dem Zugriff auf unsere Dashboards auf. Wir untersuchen das Problem und werden Sie aktualisieren, wenn wir weitere Details haben. Wir entschuldigen uns für die Unannehmlichkeiten.

2. 27. Juli 2026 um 15:24 UTCidentified

   Wir haben die Ursache des Problems identifiziert, und Dashboards sind jetzt verfügbar. Wir analysieren derzeit die Auswirkungen dieses Problems, und der Vorfall bleibt offen. Vielen Dank für Ihre Geduld.

3. 27. Juli 2026 um 16:53 UTCresolved

   Einige unserer Dienste waren von einem DNS-Problem zwischen 14:35 und 15:35 UTC betroffen. Während dieser Zeit: Die Verarbeitung von Klicks und Impressionen verzögerte sich, was zu einer vorübergehenden Erhöhung der organischen Zuordnung führte; die Onelink-API war teilweise verfügbar; und bei einigen verarbeiteten Ereignissen fehlen Geodaten. Das Problem ist vollständig gelöst. Bitte kontaktieren Sie unser Support-Team bei Fragen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. März 2026 um 04:09 UTCidentified

   We are investigating an issue that may impact the availability of appsflyer.com domain, potentially related to one of our vendors. We are assessing the impact and will share an update as more information becomes available.

2. 10. März 2026 um 05:59 UTCidentified

   Our team continues to investigate the issue affecting the availability of our main domain. Customers may experience issues accessing dashboards and sending S2S in-app events. Some customers are also reporting intermittent accessibility issues with certain APIs. We will provide further updates as more information becomes available.

3. 10. März 2026 um 08:17 UTCidentified

   Raw data export from the dashboard and the Pull API is currently unavailable. We will share further updates as more information becomes available.

4. 10. März 2026 um 10:19 UTCmonitoring

   Our teams are actively resolving this incident. During this time, customers may experience issues with campaign traffic, postbacks, click redirection, API calls, and dashboard access. We will provide further updates as more information becomes available or once the issue is fully resolved.

5. 10. März 2026 um 13:56 UTCmonitoring

   The issue affecting the availability of our domain has been resolved. Customers may still experience sporadic issues while the domain mapping change propagates. We continue to monitor the relevant services. Please note that raw data export from the dashboard and the Pull API are still unavailable. Thank you for your patience.

6. 10. März 2026 um 20:44 UTCmonitoring

   Raw data export from the dashboard and the Pull API is now available. Before exporting data, please follow the critical actions outlined in the email sent earlier today. We are aware that some customers may still experience sporadic issues while the domain mapping change propagates. Thank you again for your patience.

7. 12. März 2026 um 12:34 UTCresolved

   We are seeing significantly fewer reports related to domain mapping and expect the DNS propagation process to complete in the coming hours. We are marking this incident as resolved. If you have any questions or need assistance, our team is available to help.

1. 10. Februar 2026 um 21:08 UTCidentified

   We are investigating an issue impacting the availability of our dashboards. We will provide an update as more information becomes available.

2. 10. Februar 2026 um 21:40 UTCidentified

   We are experiencing an impact due to an Amazon CloudFront incident and are working to mitigate it. There is no impact on attribution or data processing flows. We will share updates as more information becomes available.

3. 10. Februar 2026 um 22:13 UTCmonitoring

   Dashboard availability has significantly improved. We continue to monitor the recovery and will share additional updates as information becomes available.

4. 10. Februar 2026 um 22:46 UTCresolved

   Dashboard availability has been fully restored. Our teams continue to monitor performance. If you encounter any further issues, please contact Technical Support.

1. 25. Januar 2026 um 09:35 UTCidentified

   Since approximately 09:00 UTC on Jan 25, 2026, we have observed a decrease in conversions (installs and re-engagements) attributed to TikTok, due to an increased number of errors from the TikTok Attribution API. We are closely monitoring the situation and will provide updates as soon as more information becomes available.

2. 26. Januar 2026 um 21:03 UTCresolved

   This incident has been resolved.

1. 16. Dezember 2025 um 15:39 UTCidentified

   Since approximately 11:55 UTC, we've observed a decrease in conversions (installs and reengagements) attributed to Meta, due to an increased number of errors from Meta Ads’ Attribution API. Our team is actively working with Meta, and we are waiting for a fix on Meta’s side. We are closely monitoring the situation and will provide updates as soon as more information becomes available.

2. 17. Dezember 2025 um 05:57 UTCresolved

   Meta API availability has returned to normal, and we continue to monitor conversion rates closely. We will update this page if any further anomalies occur. Thank you for your patience.

1. 26. Oktober 2025 um 11:14 UTCidentified

   We are investigating an issue with processing clicks and impressions starting from ±10:00 AM UTC. You may experience an impact on attribution to click-based networks (non-SRN). We will share updates about our investigation progress. Thank you for your patience.

2. 26. Oktober 2025 um 11:30 UTCmonitoring

   The issue with processing clicks and impressions was resolved at ±11:15 AM UTC. We process new clicks and impressions normally. Our teams are working on analyzing the impact on attribution during the issue time, and we will update you about our progress.

3. 26. Oktober 2025 um 15:02 UTCresolved

   Our teams reprocessed engagements from approximately 10:25 AM UTC to 11:15 AM UTC, and those engagements are now available for new conversions. Thank you for your patience, and please contact us for any related questions.

1. 20. September 2025 um 07:12 UTCidentified

   Since approximately 12:10 UTC, we've observed a significant decrease in conversions (installs and re-engagements) attributed to Meta, due to an increased number of errors from Meta Ads’ Attribution API. Our team is actively working with Meta, to identify the root cause and resolve this issue. We are closely monitoring the situation and will provide updates as soon as more information becomes available.

2. 20. September 2025 um 11:33 UTCresolved

   Meta API availability has returned to normal, and we continue to monitor conversion rates closely. We will update this page if any further anomalies occur. Thank you for your patience.

1. 20. August 2025 um 14:14 UTCidentified

   We have identified an issue that caused a delay of Push API data and are working to resolve it.

2. 20. August 2025 um 14:27 UTCresolved

   The Push API delay issue is resolved. The backlog of events not sent since 01:07 UTC is now being delivered and will clear over the next few hours. We’re monitoring until completion.

1. 5. August 2025 um 10:33 UTCidentified

   We have identified an issue that impacts the Integrated Partners Settings page and are working to resolve it. We apologize for the inconvenience. We'll be back with an update as soon as we have more information.

2. 5. August 2025 um 10:55 UTCresolved

   We can confirm that the issue is now resolved.

1. 1. August 2025 um 19:05 UTCidentified

   We are aware that cost, impressions, and clicks data from TikTok is missing in our dashboards and reports for today. Our team is working closely with TikTok to resolve this, and we will share an update as soon as we have more information. Thank you for your patience

2. 2. August 2025 um 13:20 UTCresolved

   The issue has been resolved and the cost, clicks and impressions data is now available in all the reports and dashboards

1. 23. Juli 2025 um 07:55 UTCmonitoring

   We are currently unable to retrieve Google SKAN data for July 21, 2025. We are actively working with the Google team and expect the data to become available by tomorrow, July 24. As a result, SKAN data for July 21 is currently missing from: The SKAN dashboard, SKAN Pull APIs, SKAN Data Locker reports, SSoT Dashboard, and Push API. We will provide an update as soon as the data is available.

2. 24. Juli 2025 um 06:31 UTCresolved

   The issue has been fully resolved, and Google SKAN data for July 21 is now available across all products. If you continue to experience any issues, please contact our support team.

1. 2. Juli 2025 um 15:04 UTCidentified

   We are currently investigating an issue affecting the attribution of new app installs to Meta. Since approximately 13:00 UTC, we've observed a ~30% decrease in recorded new installs attributed to Meta. Our team is actively working with Meta to identify the root cause and is closely monitoring the situation. We will provide updates as soon as more information becomes available.

2. 2. Juli 2025 um 17:01 UTCresolved

   Meta has resolved the issue, and the attribution to Facebook is back to normal as of 16:10 UTC.

1. 12. Juni 2025 um 19:20 UTCidentified

   We identified that a few modules are impacted by the Google Cloud Services issue. You might experience issues with downloading raw reports and pulling raw reports via the pull API. The Creative dashboard might present partial data. We are monitoring the impact and will share an update soon.

2. 12. Juni 2025 um 19:52 UTCidentified

   We are continuing to monitor the issue and are working to ensure that raw data will be fully available once the incident is resolved. Customers using Google Cloud Services to access Data Locker reports may be affected by this issue. We appreciate your patience and will provide more information as soon as it becomes available.

3. 12. Juni 2025 um 20:49 UTCmonitoring

   Raw data reports have been available for the past 20 minutes via both the dashboard and the Pull API. Additionally, the Creative Dashboard is now accessible. We continue to monitor the situation, as the underlying incident with Google Cloud Services has not yet been fully resolved. If any reports failed to generate during the incident, please re-pull them.

4. 12. Juni 2025 um 21:43 UTCresolved

   All our products and modules are now operating normally. If you are still experiencing any related issues, please contact our Customer Support team for assistance.

1. 7. Mai 2025 um 10:55 UTCidentified

   We have identified that our "Raw Data Export" page is not available and are working on fixing it. There is no impact on other components, and data is being processed normally. We will share updates as we progress.

2. 7. Mai 2025 um 11:16 UTCresolved

   The issue with the "Raw Data Export" page availability is resolved. If you're still experiencing any related issues, please reach out to customer support.

1. 24. März 2025 um 20:14 UTCidentified

   As of 19:35 UTC, new installs are attributed only to Self-Reporting Networks (SRNs) and organic sources due to an issue preventing attribution to clicks and impressions. We will provide further updates as soon as possible.

2. 24. März 2025 um 20:32 UTCidentified

   As of approximately 20:10 UTC, installs are being attributed to clicks. We are still analyzing the status of attribution to impressions. We will continue to provide updates. Thank you for your patience.

3. 24. März 2025 um 20:59 UTCresolved

   Following our analysis, starting from approximately 20:15 UTC, installs have been attributed correctly to new impressions recorded after that time. Installs will not be attributed to impressions received before 20:15 UTC. Additionally, we observed a lower rate of re-engagement attributions during the incident window (approximately 19:35–20:10 UTC). The issue has been fully resolved. If you experience any further issues, please contact our support team.

1. 16. März 2025 um 13:48 UTCidentified

   Between 12:15 UTC and 12:30 UTC, new installs were attributed only to Self-Reporting Networks (SRNs) and organic sources due to an issue preventing attribution to clicks and impressions. As of 12:30 UTC, attribution to clicks has returned to normal. However, attribution to impressions is still not functioning. We will provide further updates as soon as possible.

2. 16. März 2025 um 15:01 UTCresolved

   As of approximately 14:05 UTC, installs are being attributed to new impressions recorded after this time. Installs will not be attributed to impressions received before 14:05 UTC. The issue has now been fully resolved. If you experience any further issues, please contact our support team.

1. 6. Februar 2025 um 14:06 UTCmonitoring

   We identified an issue affecting the generation of raw data reports. While the issue has been resolved, there is still a delay in generating reports from the "Raw Data Export" page. The backlog is gradually clearing, and we expect processing times to return to normal within a few hours. We will continue to provide updates. Thank you for your patience.

2. 6. Februar 2025 um 15:21 UTCresolved

   The delay in generating raw data reports from the dashboard has been fully resolved, and operations are back to normal. Thank you again for your patience.

1. 27. Januar 2025 um 10:40 UTCidentified

   We're aware of issues presenting cost data in some of our dashboards and reports. We are working on resolving this and we'll update once we have more information to share. Thank you for your patience.

2. 27. Januar 2025 um 11:33 UTCidentified

   We are investigating the issue causing delayed or missing cost data. We will provide updates as soon as more information is available.

3. 27. Januar 2025 um 13:57 UTCresolved

   The issue is resolved. Data related to Cost reports and APIs is up to date.

1. 9. Januar 2025 um 19:17 UTCidentified

   We've identified a delay in sending Postbacks of in-apps, sessions, and installs, as well as Push API for in-apps and installs, There is no data loss and our teams are working to resolve this issue. We'll share an update on our progress as soon as possible.

2. 9. Januar 2025 um 19:59 UTCidentified

   After further investigation, the Push API service wasn’t impacted at all. In addition, Installs Postbacks are back to normal and the delay is over. We'll keep updating with any progress of closing the gap for in-apps and sessions postbacks. Thank you for your patience.

3. 9. Januar 2025 um 20:17 UTCmonitoring

   The gap for in-apps and sessions postbacks is closing. We'll update once it's back to normal.

4. 9. Januar 2025 um 21:36 UTCresolved

   The in-apps and sessions postbacks are back to normal and the issue is now fully resolved. Thank you again for your patience.