Live  /  Smartly  /  Incident

Smartly: Investigating degraded performance with Smartly reporting

Smartly · smartly.ioMinor incidentResolved2026-09-29 11:03 UTC
Public — what happened

Summary

Smartly said its reporting tools were running slower than usual, in an incident it rated as minor that began on September 29, 2026 at 09:28 UTC. The company later reported that both reporting and report exports had returned to normal, and the issue was marked resolved at 11:03 the same day. Smartly did not state a cause, but asked customers to keep report date ranges to two years or less to help manage data volumes.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 41, 2026, our weekly internet health report.

The full archive is on the Smartly status & history page.

Related: Smartly status & history. SquidGrid is not affiliated with Smartly.