Live / LiveIntent / Incident
LiveIntent: Delays in custom reports
LiveIntent · liveintent.comMinor incidentResolved2026-10-06 23:55 UTC
Public — what happened
Summary
LiveIntent said that custom report generation in its LiveIntent Platform was running late starting at 13:04 UTC on October 6, 2026, describing it as a repeat of a recent problem and rating it minor. By 16:04 UTC the company said a few reports were getting through sporadically, though most were still held up. At 19:22 UTC LiveIntent said it had found the cause, without describing it, and was rolling out a fix. The incident was marked resolved at 23:55 the same day.
Affected
Reporting API
Timeline
- Started — 2026-10-06 13:04 UTC
- Investigating — 2026-10-06 13:04 UTC (2 updates)
- Identified — 2026-10-06 19:22 UTC
- Resolved — 2026-10-06 23:55 UTC · 10h 52m 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.