Visma incident

Flyt Common solutions having performance issues

Major Resolved View vendor source →

Visma experienced a major incident on April 24, 2026 affecting Visma Flyt PPT and Visma Flyt BVV and 1 more component, lasting 2d 20h. The incident has been resolved; the full update timeline is below.

Started
Apr 24, 2026, 10:25 AM UTC
Resolved
Apr 27, 2026, 06:50 AM UTC
Duration
2d 20h
Detected by Pingoru
Apr 24, 2026, 10:25 AM UTC

Affected components

Visma Flyt PPTVisma Flyt BVVVisma Flyt HelseVisma Flyt Sikker SakFlyt Barnevern

Update timeline

  1. investigating Apr 24, 2026, 10:25 AM UTC

    We are experiencing performance problems and errors. We are investigating

  2. investigating Apr 24, 2026, 10:29 AM UTC

    We are continuing to investigate this issue.

  3. identified Apr 24, 2026, 11:23 AM UTC

    We might have encounter what the root cause is, we're looking for possibilities how to resolve it right now

  4. identified Apr 24, 2026, 11:50 AM UTC

    We're going to make an Emergency Change today at 15:00 NO time in order to resolve the degraded performance of all Flyt Common Applications. There is still on-going discussion of how change will be implemented. For now, the change will cause a downtime of ~30minutes on all FLYT Applications

  5. identified Apr 24, 2026, 01:06 PM UTC

    The fix is going to implemented. The fix will generate a total downtime of less than 5 minutes and emergency maintenance will be done in about 30 minutes, ending at around 15:30.

  6. monitoring Apr 24, 2026, 01:29 PM UTC

    Change has been implemented, we're monitoring the results

  7. resolved Apr 27, 2026, 06:50 AM UTC

    This incident has been resolved.