Live / Cadmium / Incident
Cadmium: Degraded Performance Across EthosCE
Cadmium · gocadmium.comMinor incidentResolved2026-10-30 20:13 UTC
Public — what happened
Summary
Cadmium reported a minor incident beginning at 19:55 UTC on 2026-10-29, in which sites on its EthosCE platform ran with reduced performance. The company said its internal logs server had been struggling, so it turned that server off as a precaution while it investigated. By 20:30 UTC Cadmium said it had traced the problem to a failure in its internal logging system that affected dependent sites, and that site availability had been restored. It said no course, user, or transcript data was affected, and that it was still rolling out a fix and adding safeguards, so the incident was not yet marked resolved.
Affected
EthosCE
Timeline
- Started — 2026-10-29 19:55 UTC
- Investigating — 2026-10-29 19:55 UTC
- Identified — 2026-10-29 20:30 UTC
- Monitoring — 2026-10-30 19:12 UTC
- Resolved — 2026-10-30 20:13 UTC · 24h 18m 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.