Live / Cadmium / Incident
Cadmium: Investigating
Cadmium · gocadmium.comCritical outageResolved2026-10-08 17:59 UTC
Public — what happened
Summary
Cadmium reported a service disruption, rated critical, beginning at 21:20 UTC on 2026-10-01, without saying which services or customers were affected. Two minutes later the company said it had found the underlying cause, though it did not describe what that cause was. By 21:27 UTC Cadmium said a fix was in place and service was back, and it kept watching the system before marking the incident resolved on 2026-10-08.
Affected
Elevate
Timeline
- Started — 2026-10-01 21:20 UTC
- Investigating — 2026-10-01 21:20 UTC
- Identified — 2026-10-01 21:22 UTC
- Monitoring — 2026-10-01 21:27 UTC
- Resolved — 2026-10-08 17:59 UTC · 7 days 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 41, 2026, our weekly internet health report.