Resolved after 1 hour 39 minutes, affecting Visma Net API, on April 28, 2026.
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.
Affected components
Update timeline
- investigating Apr 28, 2026, 01:30 PM UTC
We are currently investigating this issue.
- identified Apr 28, 2026, 02:11 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 28, 2026, 03:10 PM UTC
This incident has been resolved.
- postmortem Apr 30, 2026, 01:03 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.
Your product runs on more than Visma
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services