AppsFlyer Outage History
6 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded AppsFlyer Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 16, 2026 | Protect360 Dashboard avilabilityProtect360 dashboard availability has been restored. Our teams continue to monitor performance. If you encounter any further issues, please contact Technical Support. | 1h 3m | Resolved |
| Jul 27, 2026 | Dashboards availabilitySome of our services were impacted by a DNS issue between 14:35 and 15:35 UTC. During this time: clicks and impressions processing was delayed, which resulted in a temporary increase in organic attribution; the Onelink… | 1h 44m | Resolved |
| Mar 10, 2026 | appsflyer.com domain availabilityWe 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… | 56h 24m | Resolved |
| Feb 10, 2026 | Dashboard AvailabilityDashboard availability has been fully restored. Our teams continue to monitor performance. If you encounter any further issues, please contact Technical Support. | 1h 37m | Resolved |
| Jan 25, 2026 | AppsFlyer - TikTok Attribution Impact Due to TikTok Attribution API ErrorsThis incident has been resolved. | 35h 28m | Resolved |
| Dec 16, 2025 | AppsFlyer - Meta attribution impact due to errors from Meta ads’ attribution APIMeta 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. | 14h 17m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next AppsFlyer incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This AppsFlyer Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before AppsFlyer acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single AppsFlyer outage in this window ran 2d 8h, against a mean recovery of 18h 26m. If you depend on AppsFlyer in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.