Stacksync incident
Some managed databases have connectivity and cannot be reached
Stacksync experienced a major incident on February 6, 2026 affecting Current status by service (Stacksync Databases), lasting 1h 58m. The incident has been resolved; the full update timeline is below.
Affected components
Current status by service (Stacksync Databases)
Update timeline
- investigating Feb 06, 2026, 07:42 PM UTC
We're still trying to understand the root cause of the issue at the moment, this is not affecting all managed databases, only a handful of them.
- resolved Feb 06, 2026, 09:40 PM UTC
We've identified this problem, and believe negative caching of DNS records to be all that remains. We are going to continue to check for at least thirty minutes, the longest time reported for negative caching so far.