Live / Visma Cloud Services / Incident
Visma Cloud Services: Degraded performance in Flyt Foresatt
Visma Cloud Services · visma.comMinor incidentResolved2026-11-05 08:07 UTC
Public — what happened
Summary
Visma Cloud Services reported degraded performance in Flyt Foresatt, which it rated as minor, beginning at 09:07 UTC on 4 November 2026. The company said it was investigating and did not state a cause. At 14:00 UTC it said a fix was in place and it was monitoring, and by 14:21 it said logging in worked again, though some users might see a message about a partial failure and could press OK to continue. The incident was marked resolved at 08:07 UTC on 5 November.
Affected
Flyt Foresatt App
Timeline
- Started — 2026-11-04 09:07 UTC
- Investigating — 2026-11-04 09:07 UTC
- Monitoring — 2026-11-04 14:00 UTC (3 updates)
- Resolved — 2026-11-05 08:07 UTC · 23h 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.