Live / Visma Cloud Services / Incident
Visma Cloud Services: Some Visma net ERP customers are not able to access their company due to scaling failure
Visma Cloud Services · visma.comMajor incidentResolved2026-10-05 13:55 UTC
Public — what happened
Summary
Visma Cloud Services reported a major incident in which some Visma net ERP customers could not get into their company, starting at 12:04 UTC on 5 October 2026. The company said a database went offline during an infrastructure scaling operation earlier that morning, and that its cloud provider was working to restore it. A fix was put in place by 13:23 UTC, after which Visma monitored the results, and the incident was marked resolved at 13:55.
Affected
Visma Net, Visma Net API
Timeline
- Started — 2026-10-05 12:04 UTC
- Identified — 2026-10-05 12:04 UTC (2 updates)
- Monitoring — 2026-10-05 13:23 UTC
- Resolved — 2026-10-05 13:55 UTC · 1h 51m 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 42, 2026, our weekly internet health report.