Live / STACKIT / Incident
STACKIT: Unexpectedly long maintenance duration for PostgreSQL Flex instances
STACKIT · stackit.cloudMajor incidentResolved2026-10-27 21:39 UTC
Public — what happened
Summary
STACKIT reported a major incident affecting its PostgreSQL Flex database instances, starting at 19:20 UTC on 2026-10-27. The company said it first identified a fault on its platform, and about ten minutes later said the cause had been found and partly fixed while it worked to restore the remaining services. At 20:36 UTC it said that scheduled maintenance updates were taking longer per instance than planned across many systems, and that its engineers were looking into the delay and making changes to speed things up. The incident was marked resolved at 21:39 UTC.
Affected
Observability, Server Backup Management, DNS, Server Update Management, Secrets Manager, PostgreSQL Flex
Timeline
- Started — 2026-10-27 19:20 UTC
- Identified — 2026-10-27 19:20 UTC (4 updates)
- Resolved — 2026-10-27 21:39 UTC · 2h 19m 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.