On this page
Check current AppsFlyer status: statusfield.com/services/appsflyer
AppsFlyer sits between your ad spend and your attribution data. When it goes down, campaigns don't stop running — they just stop reporting correctly. Ad networks keep serving, users keep installing, but the data connecting spend to outcome silently breaks. For growth and marketing teams, that's often worse than a visible outage: budgets get misallocated before anyone notices.
Here's how to check the current status, spot what's actually broken, and respond faster when AppsFlyer has an issue.
Is AppsFlyer Down Right Now?
The fastest way to check: View live AppsFlyer status on Statusfield →
Statusfield brings together the latest recorded AppsFlyer status and incident details. Check the service page for supported components and observation timestamps; coverage depends on what the provider publishes.
How to Check AppsFlyer Status
1. Statusfield (recommended for growth teams) statusfield.com/services/appsflyer shows reported AppsFlyer component status and incident history. Configure alerts for relevant changes, and check your own event pipeline to verify campaign-data completeness.
2. AppsFlyer's Official Status Page AppsFlyer maintains its own status page covering ingestion, attribution, dashboard, and API services. It's the source of truth for confirmed incidents, but like most vendor pages it tends to lag actual customer impact — partial degradation often shows "operational" until enough customers report it.
3. Your SDK Integration Logs If the status page shows all-green but attribution numbers still look wrong, check your mobile SDK logs for failed or delayed event postbacks. A backlog on your own side can look identical to an AppsFlyer outage.
4. Growth / MarTech community channels Search "AppsFlyer down" on Twitter/X or in mobile growth Slack communities (e.g., Mobile Dev Memo, App Growth Network). Attribution issues often get flagged by other marketers before a formal incident is posted.
What Actually Breaks During an AppsFlyer Outage
AppsFlyer is a multi-service attribution platform. What breaks depends on which component fails.
| Component | What it covers | Impact when down |
|---|---|---|
| Attribution Engine | Matches clicks/impressions to installs and in-app events | Installs go unattributed or misattributed to the wrong source |
| SDK Event Ingestion | Receives in-app events from the AppsFlyer SDK | Events queue on-device or drop; conversion data delayed or lost |
| OneLink (Deep Linking) | Smart links that route users to the right app store or in-app destination | Links fail to resolve, fall back to a generic store page, or 404 |
| Dashboard / Reporting UI | Web dashboard for campaign performance | Reports fail to load or show stale/incomplete data |
| Raw Data Exports / API | Pulls attribution data into your BI stack or data warehouse | Scheduled exports fail or return partial data, breaking downstream dashboards |
| Postback Delivery | Sends attribution events to ad networks (Google, Meta, TikTok, etc.) | Ad networks don't receive conversion signals, breaking optimization algorithms |
| Fraud Protection (Protect360) | Real-time fraud filtering on installs and events | Fraud filtering pauses or over/under-blocks traffic during degradation |
A postback delivery outage is the highest-impact scenario for paid acquisition — ad networks lose the conversion signal they use to optimize spend, and campaigns can silently drift toward lower-quality traffic within hours.
Common AppsFlyer Failure Symptoms
| What you see | What it usually means |
|---|---|
| Install counts drop sharply with no real-world cause | Attribution engine delay or ingestion backlog — check before pausing campaigns |
| OneLink opens the app store instead of deep-linking in-app | OneLink resolution service degraded, falling back to default behavior |
| Ad network dashboards show installs but AppsFlyer doesn't | Postback delivery failure between AppsFlyer and the ad network |
| Dashboard shows "Data as of [stale timestamp]" | Reporting pipeline lagging behind live ingestion |
| Raw data export job fails or returns an empty file | API/export service issue, not necessarily attribution itself |
| In-app events (purchases, sign-ups) missing for a specific time window | SDK event ingestion gap — check for a corresponding status incident |
| Sudden spike in "organic" installs | Attribution misfire — paid installs falling through to organic bucket |
| Protect360 fraud scores missing or delayed | Fraud protection service degraded independently of core attribution |
Why AppsFlyer Goes Down
AppsFlyer processes attribution events at massive scale across thousands of apps and ad networks. Several things can go wrong.
Ingestion volume spikes. Major app launches, viral moments, or large UA campaign pushes can spike event volume faster than pipelines scale, causing processing delays that look like an outage.
Ad network API changes. AppsFlyer integrates with dozens of ad networks (Google, Meta, TikTok, etc.) via their APIs. When a network changes its API without notice, postback delivery or attribution matching for that network can break while everything else stays healthy.
SDK version fragmentation. Millions of app installs run different SDK versions. A bug in a specific SDK version can cause event loss for a subset of users, even when AppsFlyer's backend is fully operational.
Deployment issues. Like any large platform, AppsFlyer ships regular updates to its attribution logic and dashboard. Deployments occasionally introduce brief regressions in specific components.
Upstream cloud dependencies. AppsFlyer runs on cloud infrastructure. A regional cloud provider incident can cascade into ingestion or dashboard delays even when AppsFlyer's own code is healthy.
Privacy framework changes. iOS ATT/SKAdNetwork and Android Privacy Sandbox changes periodically require attribution logic updates. A rushed or buggy update to handle a platform change can temporarily disrupt attribution accuracy.
What To Do During an AppsFlyer Outage
For growth and marketing teams running paid acquisition, a quick response plan matters.
Immediately:
- Check Statusfield and AppsFlyer's own status page — confirm it's AppsFlyer, not an ad network or your own SDK integration
- Compare install/event counts against your ad network dashboards (Google Ads, Meta Ads Manager, TikTok) — a mismatch confirms an attribution or postback issue rather than a real drop in installs
- Pause automated bid optimization or budget-shifting rules that rely on AppsFlyer data — bad signal in, bad spend decisions out
- Notify your growth/performance marketing team so no one manually "fixes" campaigns based on incomplete data
Technical triage steps:
Check whether the gap is upstream or in your own integration: Compare raw install counts from the app stores (App Store Connect, Google Play Console) against AppsFlyer's dashboard for the same window. If store-side numbers look normal but AppsFlyer's are low, the issue is on AppsFlyer's ingestion or attribution side.
Confirm SDK events are firing: Use your mobile app's own event logging (or a lightweight local log) to confirm in-app events are actually being generated client-side, independent of whether AppsFlyer received them.
Check ad network-specific postback status: If only one network's numbers look wrong, the issue is likely a postback delivery problem specific to that integration, not a platform-wide AppsFlyer outage.
If the outage is sustained:
- Hold, don't cut, campaign budgets — pausing based on unattributed (not actually lost) installs can undo weeks of algorithm learning on ad platforms
- Contact AppsFlyer support — enterprise accounts typically have an assigned customer success or support contact for priority incidents
- Log the incident window — you'll need the exact start/end time to reconcile attribution data retroactively once AppsFlyer backfills it
After it resolves:
- Confirm AppsFlyer has backfilled attribution for the affected window (most outages are followed by a data reconciliation pass)
- Re-check ad network optimization settings that may have drifted during the gap
- Add Statusfield monitoring so your team gets alerted when AppsFlyer status changes, helping your team investigate and respond
Monitoring AppsFlyer Like a Growth Team
AppsFlyer sits in the critical path between spend and decisions. Treating it that way means monitoring it proactively.
- Set up status monitoring — Statusfield tracks AppsFlyer status continuously and alerts your team when something changes. Route notifications to email, Slack, or a webhook into your incident channel.
- Watch install-count deltas daily — a sudden, unexplained swing in install or event volume is often the first sign of an attribution issue, well before AppsFlyer posts a formal incident.
- Cross-check against ad network dashboards — treat AppsFlyer and your ad network consoles as two independent sources; a divergence between them is a strong signal.
- Track postback delivery per network — a drop specific to one ad network usually means a postback issue with that integration, not a platform-wide problem.
- Document your data-gap protocol — decide in advance how your team will handle bid optimization and reporting during an attribution gap, so no one improvises under pressure.
How to Get AppsFlyer Outage Alerts
Growth teams typically learn about AppsFlyer issues from a confused Slack thread about install numbers, not a status page. By then, campaigns have already been running on bad data for hours.
Monitor AppsFlyer on Statusfield and get alerted when AppsFlyer status changes. Route notifications to email, Slack, or a webhook that opens an incident automatically. Reporting, polling and delivery affect when updates arrive.
Frequently Asked Questions
Is AppsFlyer down right now?
Check the live status at statusfield.com/services/appsflyer for the latest recorded AppsFlyer service status, supported components and observation timestamps.
Why did my install counts suddenly drop in AppsFlyer?
A sudden drop is usually an attribution or ingestion delay, not a real decline in installs. Compare your app store console (App Store Connect or Google Play Console) install counts against AppsFlyer's dashboard for the same window — if store-side numbers look normal, the gap is on AppsFlyer's processing side.
AppsFlyer shows operational but my ad network isn't receiving conversion data — what's wrong?
This usually points to a postback delivery issue specific to that ad network integration, not a platform-wide AppsFlyer outage. Check whether other ad networks are receiving data normally; if only one is affected, the issue is likely on that specific postback pipeline.
My OneLink is opening the app store instead of deep-linking into the app — is this an outage?
It can be. When OneLink's deep-linking resolution is degraded, it typically falls back to a generic app store redirect rather than failing outright, which makes the issue easy to miss. Check Statusfield or AppsFlyer's status page for OneLink-specific incidents.
Should I pause my ad campaigns during an AppsFlyer outage?
Generally no — pause automated bid or budget optimization rules that depend on AppsFlyer data instead of pausing the campaigns themselves. Installs during the outage are usually real; only the attribution reporting is affected, and AppsFlyer typically backfills the data once the incident resolves.
How do I get alerts when AppsFlyer goes down?
Set up AppsFlyer monitoring on Statusfield. You'll get notifications for detected changes via email or webhooks when AppsFlyer status changes, so your growth team knows before campaign data looks wrong for hours.
Does AppsFlyer backfill attribution data after an outage?
In most cases, yes — once ingestion and attribution processing resume, AppsFlyer typically reconciles the affected window and backfills accurate attribution data. Confirm the backfill has completed before drawing conclusions from campaign performance during the incident window.
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.