Live / Visma Cloud Services / Incident
Visma Cloud Services: Investigating issue on Flyt Skole production
Visma Cloud Services · visma.comCritical outageResolved2026-11-05 19:24 UTC
Public — what happened
Summary
Visma Cloud Services reported a critical problem with the production version of its Flyt Skole application, which it said was intermittently unavailable. The company began investigating at 14:18 UTC on 2026-11-05 and said it had found the problem about nine minutes later, at 14:27 UTC. It reported putting a fix in place at 15:19 UTC and then watching how things went, and the incident was marked resolved at 19:24.
Affected
Flyt Skole, Flyt Skole API
Timeline
- Started — 2026-11-05 14:18 UTC
- Investigating — 2026-11-05 14:18 UTC
- Identified — 2026-11-05 14:27 UTC
- Monitoring — 2026-11-05 15:19 UTC
- Resolved — 2026-11-05 19:24 UTC · 5h 06m 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.