Live / Visma Cloud Services / Incident
Visma Cloud Services: We are currently investigating an issue with Visma.net Employee service
Visma Cloud Services · visma.comMinor incidentResolved2026-11-02 14:15 UTC
Public — what happened
Summary
Visma Cloud Services said it was looking into a problem with its Visma.net Employee service that affected changing existing employee records or creating new ones. The company began investigating at 13:11 UTC on 2026-11-02 and rated the issue as minor. It said at 13:37 UTC that it had found the problem and was working on a fix, and by 13:40 UTC it said a fix was in place and it was watching the results. The incident is marked resolved as of 14:15.
Affected
Employee Management
Timeline
- Started — 2026-11-02 13:11 UTC
- Investigating — 2026-11-02 13:11 UTC (2 updates)
- Identified — 2026-11-02 13:37 UTC
- Monitoring — 2026-11-02 13:40 UTC
- Resolved — 2026-11-02 14:15 UTC · 1h 04m 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.