Affected components
Update timeline
- investigating Apr 24, 2026, 10:25 AM UTC
We are experiencing performance problems and errors. We are investigating
- investigating Apr 24, 2026, 10:29 AM UTC
We are continuing to investigate this issue.
- 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
- 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
- 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.
- monitoring Apr 24, 2026, 01:29 PM UTC
Change has been implemented, we're monitoring the results
- resolved Apr 27, 2026, 06:50 AM UTC
This incident has been resolved.
Looking to track Visma downtime and outages?
Pingoru polls Visma's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Visma reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Visma alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required