Historial de interrupciones de Adjust

1. August 15, 2026 at 7:32 AM UTCinvestigating

   El servicio de control y presentación de informes de Adjust está experimentando una degradación en el rendimiento. Nuestros ingenieros están investigando el tema

2. August 15, 2026 at 7:33 AM UTCidentified

   El servicio de control y presentación de informes de Adjust está experimentando una degradación en el rendimiento. Hemos identificado los temas y nuestros ingenieros están trabajando en la resolución.

3. August 15, 2026 at 8:09 AM UTCresolved

   El incidente está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 5, 2026 at 5:05 AM UTCinvestigating

   We are currently investigating several reporting issues. Ad Spend data is missing for all clients using cron schedules, affecting part of yesterday's data and today's data, while clients using custom schedules via the Scheduling Service appear to be unaffected. We are also observing intermittent cases of missing tracker names in reports.

2. June 5, 2026 at 6:30 AM UTCidentified

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

3. June 5, 2026 at 7:13 AM UTCidentified

   We have successfully restored the majority of the missing Ad Spend data and resolved the intermittent issue with missing tracker names in reports. Our team is actively working to restore the remaining Ad Spend data.

4. June 5, 2026 at 11:24 AM UTCresolved

   This incident has been resolved.

1. April 23, 2026 at 10:55 AM UTCinvestigating

   We’re investigating intermittent errors and elevated latency affecting a subset of incoming requests.

2. April 23, 2026 at 10:56 AM UTCresolved

   This incident has been resolved.

1. April 11, 2026 at 3:48 AM UTCinvestigating

   We are currently investigating degraded performance of the Deeplink Generator API, dashboard and reporting services. Our engineers are actively working on resolving the issue.

2. April 11, 2026 at 4:10 AM UTCresolved

   This incident has been resolved.

1. March 17, 2026 at 8:31 PM UTCinvestigating

   We are currently investigating an issue that is causing partial delays in raw data (CSV) exports. No data loss is expected.

2. March 18, 2026 at 12:41 AM UTCmonitoring

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

3. March 18, 2026 at 2:49 PM UTCresolved

   This incident has been resolved.

1. March 16, 2026 at 8:27 AM UTCinvestigating

   We are currently investigating an issue that is preventing the ingestion of aggregated ad spend data, the validation of in-app purchases, and the ingestion of SKAN data from the Meta and Google Ads reporting APIs.

2. March 16, 2026 at 10:32 AM UTCinvestigating

   We are continuing to investigate this issue.

3. March 16, 2026 at 4:54 PM UTCresolved

   This incident has been resolved.

1. March 3, 2026 at 12:35 PM UTCidentified

   We are currently investigating an issue that is causing partial delays in raw data (CSV) exports. No data loss is expected.

2. March 5, 2026 at 1:14 PM UTCresolved

   This incident has been resolved.

1. February 27, 2026 at 9:28 AM UTCinvestigating

   We are currently experiencing degraded performance on dashboard, report service and automate services. Our engineers are working on resolving the issue.

2. February 27, 2026 at 9:47 AM UTCidentified

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

3. February 27, 2026 at 9:48 AM UTCmonitoring

   The fix has been implemented, services are available and we're continuing to monitor the status.

4. February 27, 2026 at 10:45 AM UTCresolved

   The incident has been resolved.

1. February 17, 2026 at 11:09 AM UTCidentified

   We have identified an issue causing processing delays for a small subset of incoming data from February 16, 2026. Our engineering team is currently implementing a fix. Please note that no data has been lost, and all records remain queued for processing.

2. February 17, 2026 at 3:05 PM UTCresolved

   This incident has been resolved.

1. February 9, 2026 at 12:51 PM UTCidentified

   We are currently experiencing a degraded performance on our dashboard. Our engineers have identified the root cause and are working on resolving the issue.

2. February 9, 2026 at 1:24 PM UTCresolved

   The issue has been resolved.

1. January 27, 2026 at 7:45 PM UTCmonitoring

   We're currently experiencing a data processing delay of about 5% of today’s data for non-SAN data. Our engineers are actively working on resolving this delay.

2. January 27, 2026 at 9:07 PM UTCresolved

   The delay has been resolved.

1. January 18, 2026 at 11:59 AM UTCidentified

   We are currently experiencing a delay in processing revenue events that occurred between 0:15 and 3:08 UTC. The delay will be resolved within the same day on 18th of January.

2. January 18, 2026 at 11:59 AM UTCmonitoring

   We are working on resolving the delay, it will be resolved within the same day on 18th of January.

3. January 21, 2026 at 10:01 PM UTCresolved

   The incident has been resolved.

1. January 14, 2026 at 1:10 PM UTCresolved

   The issue occurred between 11:55–12:25 UTC and has been fully resolved.

1. December 13, 2025 at 4:54 AM UTCinvestigating

   The Adjust dashboard is currently experiencing a degradation in performance. This disruption has no impact on any of the attribution data with Adjust, including any of your active advertising campaigns. All raw data exports including real-time callbacks and CSV uploads, both to your own BIs and to partners, will function as normal. We are working on fixing this issue.

2. December 13, 2025 at 7:05 AM UTCmonitoring

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

3. December 13, 2025 at 7:16 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. January 9, 2026 at 3:31 PM UTCresolved

   This incident has been resolved.

1. October 22, 2025 at 12:47 PM UTCinvestigating

   We are currently experiencing degraded performance for our dashboard. The engineering team is actively working on resolving the issue.

2. October 22, 2025 at 4:01 PM UTCidentified

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

3. October 22, 2025 at 5:28 PM UTCresolved

   This incident has been resolved.

1. September 22, 2025 at 1:35 PM UTCinvestigating

   We are currently experiencing degraded performance for our dashboard. The engineering team is actively working on resolving the issue.

2. September 22, 2025 at 1:36 PM UTCresolved

   The issue has been resolved, all services are fully operational.

1. August 28, 2025 at 12:15 PM UTCinvestigating

   Adjust is currently experiencing a service outage. As a result, some Adjust tracker URLs fail to redirect, incoming engagements and s2s requests are partly not being processed. We sincerely apologize for the disruption and inconvenience caused. We have all teams active to collectively work on an immediate solution.

2. August 28, 2025 at 12:39 PM UTCinvestigating

   We are continuing to investigate this issue.

3. August 28, 2025 at 1:05 PM UTCidentified

   We identified the root cause and are working on resolving the issue.

4. August 28, 2025 at 1:35 PM UTCidentified

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

5. August 28, 2025 at 2:01 PM UTCidentified

   A fix has been implemented, we are continuing to monitor the situation.

6. August 28, 2025 at 2:03 PM UTCidentified

   We are continuing to monitor the implemented fix.

7. August 28, 2025 at 2:15 PM UTCmonitoring

   We are continuing to monitor the implemented fix.

8. August 28, 2025 at 4:45 PM UTCresolved

   All systems are operational, the team is continuing to monitor and working on the data and attribution recovery.

1. August 4, 2025 at 11:45 AM UTCidentified

   We're experiencing an elevated level of server response errors and are currently looking into the issue.

2. August 4, 2025 at 12:23 PM UTCmonitoring

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

3. August 4, 2025 at 12:35 PM UTCresolved

   All systems are operational.

1. May 27, 2025 at 9:54 AM UTCmonitoring

   We're currently experiencing a delay in data processing for Report Service as well as raw Data Exports. There is no impact on any of the attribution data with Adjust, including any of your active advertising campaigns. We expect full resolution, including callbacks and dashboard reporting, by 11am UTC.

2. May 28, 2025 at 4:58 AM UTCresolved

   This incident has been resolved.

1. May 23, 2025 at 10:21 AM UTCidentified

   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. May 23, 2025 at 10:58 AM UTCidentified

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

3. May 23, 2025 at 11:55 AM UTCidentified

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

4. May 23, 2025 at 12:30 PM UTCmonitoring

   We're continuing to monitor and improve availability

5. May 23, 2025 at 6:54 PM UTCmonitoring

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

6. May 23, 2025 at 7:12 PM UTCmonitoring

   We are continuing to monitor for any further issues.

7. May 24, 2025 at 7:47 AM UTCidentified

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

8. May 24, 2025 at 12:26 PM UTCmonitoring

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

9. May 24, 2025 at 6:07 PM UTCmonitoring

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

10. May 27, 2025 at 9:16 AM UTCresolved

    This incident has been resolved.