Live / STACKIT / Incident
STACKIT: STACKIT Identity Provider returning 503s
STACKIT · stackit.cloudCritical outageResolved2026-10-31 17:53 UTC
Public — what happened
Summary
STACKIT said its Identity Provider was returning 503 errors, and it rated the incident critical. The company reported a fault on its platform at 16:16 UTC on 2026-10-31 and said its team was working to find and fix the cause. By 16:22 UTC it said the problem had been fixed and it was closely watching the affected components, and it asked anyone still seeing issues to contact support. The incident was marked resolved at 17:53 UTC.
Affected
Cloud Identity
Timeline
- Started — 2026-10-31 16:16 UTC
- Identified — 2026-10-31 16:16 UTC
- Monitoring — 2026-10-31 16:22 UTC
- Resolved — 2026-10-31 17:53 UTC · 1h 37m 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 45, 2026, our weekly internet health report.