Live / STACKIT / Incident
STACKIT: STACKIT Incident: SKE – STACKIT Kubernetes Engine (Control Plane)
STACKIT · stackit.cloudMajor incidentResolved2026-11-12 10:05 UTC
Public — what happened
Summary
STACKIT said that starting at 08:40 UTC on 2026-11-12 a number of control planes for its Kubernetes Engine service could not be reached. The company stated that workloads already running were not affected, and it described the issue as a fault it had identified on its platform. Its team said it was investigating the cause and working on a fix, and the incident was later marked resolved at 10:05.
Affected
Kubernetes Engine
Timeline
- Started — 2026-11-12 08:40 UTC
- Identified — 2026-11-12 08:40 UTC
- Resolved — 2026-11-12 10:05 UTC · 1h 25m 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 STACKIT 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 STACKIT: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the STACKIT report →
More from STACKIT
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.