Live / Visma Cloud Services / Incident
Visma Cloud Services: Degradated performance in Visma.net Payslip
Visma Cloud Services · visma.comMinor incidentResolved2026-10-30 12:33 UTC
Public — what happened
Summary
Visma Cloud Services reported slower than normal performance in its Visma.net Payslip service, which it classed as a minor issue. It said the problem began at 11:10 UTC on 2026-10-30, and a minute later it said it had identified the cause as throttling related to logging, which made processing too slow. The company said it was working on a fix, and the incident was marked resolved at 12:33.
Affected
Visma.net Payslip
Timeline
- Started — 2026-10-30 11:10 UTC
- Investigating — 2026-10-30 11:10 UTC
- Identified — 2026-10-30 11:11 UTC
- Resolved — 2026-10-30 12:33 UTC · 1h 23m 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 45, 2026, our weekly internet health report.