Visma experienced a minor incident on April 28, 2026 affecting Visma Net and Visma Net API, lasting 17h 14m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 28, 2026, 08:43 PM UTC
We are currently investigating this issue.
- monitoring Apr 29, 2026, 02:34 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 29, 2026, 05:21 AM UTC
We are continuing to monitor for any further issues.
- monitoring Apr 29, 2026, 06:41 AM UTC
We are continuing to monitor for any further issues.
- investigating Apr 29, 2026, 07:17 AM UTC
We are currently investigating this issue.
- identified Apr 29, 2026, 08:02 AM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 29, 2026, 09:11 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Apr 29, 2026, 10:07 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 29, 2026, 10:39 AM UTC
We are continuing to monitor for any further issues.
- resolved Apr 29, 2026, 01:57 PM UTC
This incident has been resolved.
- postmortem Apr 30, 2026, 12:47 PM UTC
Root cause was a change 10.94.0 related to authentication change where we wanted to optimize the flow of getting authentication tokens from Connect. The goal was to lower the amount of token requests towards Connect and therefore the risk of being throttled. Unfortunately the change led to a locking of threads on some application servers which caused timeouts and degraded performance for some of our customers. We were able to mitigate the problem with a patch by rolling back the change. Monitoring showed that we are back to normal again.