Live  /  Smartly  /  Incident

Smartly: Investigating degraded performance with Reporting

Smartly · smartly.ioMajor incidentResolved2026-09-23 16:32 UTC
Public — what happened

Summary

Smartly reported a major incident involving slower or degraded performance in its Reporting feature, beginning on September 23, 2026 at 14:39 UTC. The company did not say which customers were affected or what caused the problem. Smartly later said Reporting was working normally again, and the incident was marked resolved at 16:32 the same day.

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 40, 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.