Adjust incident

Adjust Service Outage - Monitoring

Major Resolved View vendor source →

Adjust experienced a major incident on May 23, 2025 affecting Engagement Redirect Endpoint and SDK Endpoint and 1 more component, lasting 2d 21h. The incident has been resolved; the full update timeline is below.

Started
May 23, 2025, 10:21 AM UTC
Resolved
May 26, 2025, 08:17 AM UTC
Duration
2d 21h
Detected by Pingoru
May 23, 2025, 10:21 AM UTC

Affected components

Engagement Redirect EndpointSDK EndpointServer to Server Endpoint

Update timeline

  1. identified May 23, 2025, 10:21 AM UTC

    Adjust is currently experiencing a service outage. The issue has been identified as a DDoS attack and a fix is being implemented. While the issue is present, a significant portion of Adjust tracker URLs can fail to redirect, all incoming engagements and s2s requests aren't processed in full. Requests such as installs, sessions, and events sent by the Adjust SDK are not being processed but they will be buffered locally on each device and replayed in full once our services are back online. We sincerely apologize for the disruption and inconvenience caused.

  2. identified May 23, 2025, 10:58 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified May 23, 2025, 11:55 AM UTC

    We've deployed initial protection measures, some endpoints still exist in a degraded state and we are working towards a permanent fix

  4. monitoring May 23, 2025, 12:30 PM UTC

    We're continuing to monitor and improve availability

  5. monitoring May 23, 2025, 06:54 PM UTC

    Permanent fix is in place, and indications are that services are fully operational. We are continuing to monitor the situation.

  6. monitoring May 23, 2025, 07:12 PM UTC

    We are continuing to monitor for any further issues.

  7. identified May 24, 2025, 07:31 AM UTC

    The issue has been identified and a fix is being implemented.

  8. identified May 24, 2025, 07:47 AM UTC

    The issue has been identified and a fix is being implemented.

  9. monitoring May 24, 2025, 12:26 PM UTC

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

  10. monitoring May 24, 2025, 06:07 PM UTC

    The deployment of mitigation measures has been completed, and service availability is fully operational. We are continuing to monitor the situation closely.

  11. resolved May 27, 2025, 09:16 AM UTC

    This incident has been resolved.