Live / STACKIT / Incident
STACKIT: STACKIT Incident - VM creation (especially SKE) partially impaired
STACKIT · stackit.cloudMinor incidentResolved2026-10-01 11:00 UTC
Public — what happened
Summary
STACKIT reported a minor problem on its platform on 2026-10-01, beginning at 07:48 UTC, in which some virtual machines, particularly those in its SKE environment, could not be started or scaled properly in certain cases. The company said it had found a fault on the platform shortly afterward but did not describe what the underlying cause was. At 10:33 UTC STACKIT said the cause had been fixed and it was watching the affected components, and the incident was marked resolved at 11:00.
Timeline
- Started — 2026-10-01 07:48 UTC
- Investigating — 2026-10-01 07:48 UTC
- Identified — 2026-10-01 07:50 UTC (2 updates)
- Monitoring — 2026-10-01 10:33 UTC
- Resolved — 2026-10-01 11:00 UTC · 3h 12m 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 41, 2026, our weekly internet health report.