3rd Party: Some AppLovin connectors are failing

Update timeline

1. identified Jul 06, 2026, 11:05 PM UTC

   The issue has been identified and we are working to resolve it.

2. identified Jul 06, 2026, 11:12 PM UTC

   We have identified an issue with the AppLovin connector where syncs for the advertiser_report table are failing with HTTP 500 Internal Server Errors. This is caused by a query timeout on AppLovin's backend — the expanded column set being requested exceeds AppLovin's server-side query execution limit. We are actively working on a fix and will provide further updates.

3. monitoring Jul 06, 2026, 11:45 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Jul 07, 2026, 12:01 AM UTC

   We have applied a fix that resolves the 500 internal server error for the advertiser_report table. Affected connectors should resume syncing normally. We are monitoring recovery across all affected accounts.

5. resolved Jul 07, 2026, 01:41 AM UTC

   This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We have identified an issue with the AppLovin connector where syncs are failing with HTTP 500 Internal Server Error. Timeline: The issue began on July 6, 2026, at 8:30 PM UTC and was resolved on July 6, 2026, at 10:00 PM UTC. Cause: The failures were caused by a backend issue on AppLovin’s side, resulting in API requests timing out or returning HTTP 500 errors. Some syncs were also impacted by increased query complexity due to an expanded set of requested fields, which exceeded AppLovin’s server-side query execution limits. Resolution: AppLovin resolved the backend issue on their end, after which connections using the /skaReport endpoint began syncing successfully again. We rolled back the expanded column set for affected customers. This mitigation reduced query complexity and allowed impacted connections to resume syncing successfully