Live / Cadmium / Incident
Cadmium: Degraded Performance across Elevate
Cadmium · gocadmium.comMinor incidentResolved2026-10-27 14:20 UTC
Public — what happened
Summary
Cadmium reported a minor incident it called degraded performance across Elevate, which began on 2026-10-26 at 13:48 UTC when it said it noticed a service disruption. By 14:08 UTC the company said it had found the root cause, and at 14:15 UTC it said a fix was in place and service had been restored while it kept monitoring. The incident was marked resolved on 2026-10-27 at 14:20. Cadmium did not say who was affected or give details about the cause.
Affected
Elevate, Conference365
Timeline
- Started — 2026-10-26 13:48 UTC
- Investigating — 2026-10-26 13:48 UTC
- Identified — 2026-10-26 14:08 UTC
- Monitoring — 2026-10-26 14:15 UTC
- Resolved — 2026-10-27 14:20 UTC · 24h 32m 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 Cadmium 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 Cadmium: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Cadmium report →
More from Cadmium
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.