NextRoll Outage History
14 incidents recorded over the last 365 days, 10 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 NextRoll Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 17, 2026 | Engineering team is investigating an issue preventing ABM campaigns and Playbooks from spendingThis incident has been resolved. | 139h 35m | Resolved |
| Jun 9, 2026 | Engineering team is investigating an issue preventing campaigns that are targeting a list of zip codes from spendingThis incident has been resolved. | 16h 40m | Resolved |
| May 20, 2026 | Users are unable log into their AdRoll accounts due to SSO issues.This incident has been resolved. | 1h 34m | Resolved |
| Apr 30, 2026 | [Planned Maintenance 2026-04-30] Ads database scheduled maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 28, 2026 | [Planned Maintenance 2026-04-27] Pixel database scheduled maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Apr 7, 2026 | [Planned Maintenance 2026-04-07] Pixel database scheduled maintenanceThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Apr 3, 2026 | Workflow reports are currently unavailable for downloading.This incident has been resolved. | 36 min | Resolved |
| Feb 26, 2026 | Delays in processing reportingThis incident has been resolved. | 4h 26m | Resolved |
| Feb 24, 2026 | [Planned Outage 2026-02-24] AdRoll ABM database upgradeThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Jan 22, 2026 | Users are unable to make updates to recipe campaigns via the dashboard.This incident has been resolved. | 1h 57m | Resolved |
| Jan 14, 2026 | Unable to create/modifiy Attribute-type audiencesThis incident has been resolved. | 4h 54m | Resolved |
| Jan 12, 2026 | Incomplete reporting data from 1/8/2026-1/12/2026This incident has been resolved. | 91h 31m | Resolved |
| Jan 9, 2026 | Setting up e-commerce integration shows errors for some customers.This incident is now resolved. | 13h 33m | Resolved |
| Nov 11, 2025 | The engineering team is investigating reports of dashboard loading issues with a subset of campaigns.This incident has been resolved. | 5h 25m | Resolved |
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 NextRoll 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 NextRoll 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 NextRoll 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 NextRoll outage in this window ran 5d 19h, against a mean recovery of 20h 22m. If you depend on NextRoll 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.