Adtraction Outage History

17 incidents recorded over the last 365 days, 16 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.

Live Adtraction status100.00% uptime history

Every Recorded Adtraction Incident

Adtraction incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Scheduled maintenanceScheduled maintenance is currently in progress. We will provide updates as necessary.30 minScheduled
Oct 13, 2026Service disruption affecting webThis incident has been resolved.3h 22mResolved
Sep 21, 2026Service disruption affecting webThis incident has been resolved.4h 22mResolved
Sep 15, 2026Service disruption affecting multiple Adtraction servicesThis incident has been resolved.1h 20mResolved
Jul 16, 2026Service disruption affecting partner platformThis incident has been resolved.5h 12mResolved
Jun 22, 2026Service disruption affecting webThis incident has been resolved.1h 26mResolved
May 20, 2026Web service disruptionThis incident has been resolved.17h 4mResolved
May 11, 2026Service disruption affecting Web and APIThis incident has been resolved.2h 58mResolved
May 3, 2026Web service disruptionThis incident has been resolved.2h 35mResolved
Mar 30, 2026Service disruption affecting webThis incident has been resolved.6h 8mResolved
Mar 19, 2026Service disruption affecting webThis incident has been resolved.12h 0mResolved
Mar 18, 2026Service disruption affecting webThis incident has been resolved.1h 44mResolved
Mar 18, 2026Service disruptionThis incident has been resolved.1h 22mResolved
Mar 17, 2026Service disruption affecting webThis incident has been resolved.44 minResolved
Mar 15, 2026Web service disruptionWe're currently experiencing issues with access to web. Our team is investigating and working to resolve the problem. Incident has bee resolved.-9 minResolved
Feb 13, 2026Service disruption affecting Api and WebThis incident has been resolved.26 minResolved
Nov 7, 2025Service disruption reportingThis incident has been resolved.3h 59mResolved

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 Adtraction 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 Adtraction 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 Adtraction 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 Adtraction outage in this window ran 17h 4m, against a mean recovery of 4h 5m. If you depend on Adtraction 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.