Live / Visma Cloud Services / Incident
Visma Cloud Services: Medvind databases unavailable
Visma Cloud Services · visma.comMajor incidentResolved2026-10-24 09:39 UTC
Public — what happened
Summary
Visma Cloud Services reported a major incident in which databases for its Medvind service were unavailable. The company said it began looking into the problem at 08:54 UTC on 2026-10-24. By 09:12 UTC it said the issue had been identified and a fix was being put in place, and the incident was marked resolved at 09:39. The company did not say in its updates what caused the problem or how many customers were affected.
Timeline
- Started — 2026-10-24 08:54 UTC
- Investigating — 2026-10-24 08:54 UTC
- Identified — 2026-10-24 09:12 UTC
- Resolved — 2026-10-24 09:39 UTC · 45 min 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 Visma Cloud Services 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 Visma Cloud Services: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Visma Cloud Services report →
More from Visma Cloud Services
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.