Live / Cornerstone / Incident
Cornerstone: Latency on Reporting 2.0 - UK SL2 swimlane
Cornerstone · csod.comMajor incidentResolved2026-10-06 18:48 UTC
Public — what happened
Summary
Cornerstone reported slowdowns in its Reporting 2.0 feature for the UK SL2 swim lane starting at 13:13 UTC on 2026-10-06, saying customers with portals there could face delays or trouble opening Analytics reports. The company said a fix applied by 13:47 UTC brought performance back, but the problem returned around 14:44 UTC. Cornerstone said a further change put in place by 16:30 UTC restored normal reporting, and after a period of observation the incident was marked resolved at 18:48 UTC. No cause was given in their updates.
Affected
Reporting 2.0
Timeline
- Started — 2026-10-06 13:13 UTC
- Investigating — 2026-10-06 13:13 UTC
- Monitoring — 2026-10-06 13:47 UTC
- Investigating — 2026-10-06 14:44 UTC
- Monitoring — 2026-10-06 16:30 UTC
- Resolved — 2026-10-06 18:48 UTC · 5h 35m 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 Cornerstone 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 Cornerstone: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Cornerstone report →
More from Cornerstone
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.