Live / Smartly / Incident
Smartly: Intelligence features experiencing issues in Smartly
Smartly · smartly.ioMinor incidentResolved2026-10-30 10:35 UTC
Public — what happened
Summary
Smartly reported a minor incident that began on 2026-10-28 at 14:53 UTC, when Trigger Sets and Reporting were slow, with some users seeing them hang or fail to open. The company said running ads should keep delivering throughout. By 16:39 UTC it said Reporting and Triggers were working again, but it was then looking into problems with Creative Insights. Later that day Smartly said the Creative Insights problem affected only grouping of new assets, while existing groupings and other features still worked, and the incident was marked resolved on 2026-10-30 at 10:35.
Affected
Reporting
Timeline
- Started — 2026-10-28 14:53 UTC
- Investigating — 2026-10-28 14:53 UTC (2 updates)
- Identified — 2026-10-28 16:39 UTC (3 updates)
- Resolved — 2026-10-30 10:35 UTC · 43h 42m 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 Smartly 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 Smartly: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Smartly report →
More from Smartly
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.