Live / Cornerstone / Incident
Cornerstone: Latency on JP SL1 PRD
Cornerstone · csod.comMajor incidentResolved2026-10-30 02:12 UTC
Public — what happened
Summary
Cornerstone reported a major incident beginning at 01:24 UTC on 2026-10-30 affecting its JP SL1 swim lane, first describing it as slow handling of background tasks such as email and LAT processing. At 01:40 UTC the company corrected this, saying the real problem was system latency, which could cause delays or trouble reaching some pages for clients with portals in that swim lane. By 01:56 UTC Cornerstone said the latency had eased and it was monitoring, and the incident was marked resolved at 02:12 UTC. No cause was given in the updates.
Affected
Response Time
Timeline
- Started — 2026-10-30 01:24 UTC
- Investigating — 2026-10-30 01:24 UTC (2 updates)
- Monitoring — 2026-10-30 01:56 UTC
- Resolved — 2026-10-30 02:12 UTC · 48 min 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 45, 2026, our weekly internet health report.