Live / LiveIntent / Incident
LiveIntent: Delays in custom reports generation
LiveIntent · liveintent.comMinor incidentResolved2026-10-05 22:09 UTC
Public — what happened
Summary
LiveIntent said that on 2026-10-05 at 13:22 UTC it found a problem causing custom reports in the LiveIntent Platform to be generated late for users. By 14:30 UTC the company said it had pinpointed the issue with scheduled reports, while noting that real-time reports were unaffected; it did not describe the cause publicly. LiveIntent warned that recovery could take several hours, reported a fix in place at 20:33 UTC while data was still being processed, and marked the incident resolved at 22:09.
Affected
Scheduled Reports
Timeline
- Started — 2026-10-05 13:22 UTC
- Investigating — 2026-10-05 13:22 UTC
- Identified — 2026-10-05 14:30 UTC (3 updates)
- Monitoring — 2026-10-05 20:33 UTC
- Resolved — 2026-10-05 22:09 UTC · 8h 47m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach LiveIntent against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for LiveIntent: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the LiveIntent report →
More from LiveIntent
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.