Live / Visma Cloud Services / Incident
Visma Cloud Services: Limited access to Visma HoP andIntegration services
Visma Cloud Services · visma.comMajor incidentResolved2026-11-02 07:48 UTC
Public — what happened
Summary
Visma Cloud Services said users had trouble reaching its Visma HoP and Integration services, and it rated the incident as major. The problem was first reported at 07:01 UTC on 27 October 2026. About half an hour later the company said it had identified the issue and was working on a fix, and by 07:57 UTC it said a fix was in place and it was watching the results. The incident was marked resolved on 2 November 2026 at 07:48 UTC.
Affected
Visma Horizon, Visma HoP
Timeline
- Started — 2026-10-27 07:01 UTC
- Investigating — 2026-10-27 07:01 UTC
- Identified — 2026-10-27 07:32 UTC
- Monitoring — 2026-10-27 07:57 UTC
- Resolved — 2026-11-02 07:48 UTC · 6 days 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.