Adjust Outage History

22 incidents recorded over the last 365 days, 20 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 Adjust Incident

Adjust incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 20, 2026Degraded backend performanceThis incident has been resolved.36 minResolved
Oct 19, 2026Adjust Dashboard AccessThis incident has been resolved.9 minResolved
Oct 15, 2026Dashboard Email Delivery Delay(UTC 4:10) The delivery delays impacting 2FA, password reset, and invitation emails have been fully resolved. Our third-party email provider has cleared the backlog, and all email services are operating normally.0 minResolved
Oct 7, 2026Degraded performance of engagement redirectsThis incident has been resolved.39 minResolved
Sep 10, 2026Degraded performance on deeplinksThis incident has been resolved.-14 minResolved
Sep 10, 2026Degraded performance on deeplinksWe've received reports that in some environments TrueLink URLs lead users to the store instead of the installed apps. the team is investigating4 minResolved
Aug 15, 2026Degraded performance of dashboard and reporting APIsThe incident is resolved.3h 21mResolved
Jun 11, 2026Audience Builder MaintenanceThe scheduled maintenance has been completed.9h 0mScheduled
Jun 5, 2026Missing Ad Spend data and missing tracker names in reportsThis incident has been resolved.5h 55mResolved
Apr 23, 2026Degraded PerformanceThis incident has been resolved.15 minResolved
Apr 11, 2026Degraded performance of Deeplink Generator API, dashboard and reporting servicesThis incident has been resolved.2h 30mResolved
Mar 17, 2026Raw Data Export – Partial DelaysThis incident has been resolved.20h 29mResolved
Mar 16, 2026Partial data processing delayThis incident has been resolved.6h 3mResolved
Mar 3, 2026Raw Data Export – Partial DelaysThis incident has been resolved.36h 0mResolved
Feb 27, 2026Degraded performance on dashboard, report service and automate servicesThe incident has been resolved.2h 32mResolved
Feb 17, 2026Degraded data processing for 2026-02-16This incident has been resolved.14h 59mResolved
Feb 9, 2026Degraded performance - dashboardThe issue has been resolved.1h 21mResolved
Jan 27, 2026Data processing delayThe delay has been resolved.3h 29mResolved
Jan 18, 2026Revenue events delayThe incident has been resolved.65h 44mResolved
Jan 14, 2026Degraded performance dashboardThe issue occurred between 11:55–12:25 UTC and has been fully resolved.0 minResolved
Dec 13, 2025Degraded performance dashboardThis incident has been resolved.3h 14mResolved
Nov 20, 2025Audience Builder MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled

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 Adjust 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 Adjust 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 Adjust 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 Adjust outage in this window ran 2d 17h, against a mean recovery of 8h 27m. If you depend on Adjust 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.