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

As listed on Visma Cloud Services’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Visma Cloud Services status & history page.

Related: Visma Cloud Services status & history. SquidGrid is not affiliated with Visma Cloud Services.