Live / Visma Cloud Services / Incident
Visma Cloud Services: Provisioning of new companies failing in Visma net
Visma Cloud Services · visma.comMinor incidentResolved2026-11-03 14:30 UTC
Public — what happened
Summary
Visma Cloud Services said that setting up new companies in Visma net was failing, and it rated the problem as minor. The company reported that it had found the issue on 2 November 2026 at 12:15 UTC and planned to include a fix in a release on 3 November. It also said it would re-run the setup processes that had failed once that release was out. The incident is now marked resolved, with the resolution recorded on 3 November at 14:30.
Affected
Visma Net
Timeline
- Started — 2026-11-02 12:15 UTC
- Identified — 2026-11-02 12:15 UTC
- Resolved — 2026-11-03 14:30 UTC · 26h 15m 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 46, 2026, our weekly internet health report.