Visma incident
Degraded performance in Visma net after release of 11.0.9
Visma experienced a notice incident on August 26, 2026 affecting Visma Net and Visma Net API, lasting 4h 21m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 26, 2026, 07:30 AM UTC
We are currently investigating this issue.
- identified Aug 26, 2026, 07:51 AM UTC
We see degraded performance on UI and API. Also on Visma Approval is affected.
- identified Aug 26, 2026, 07:52 AM UTC
We are continuing to work on a fix for this issue.
- identified Aug 26, 2026, 07:52 AM UTC
We are continuing to work on a fix for this issue.
- identified Aug 26, 2026, 08:32 AM UTC
We are implementing a fix at the moment. Estimated time to production is 2 hours.
- identified Aug 26, 2026, 10:58 AM UTC
Fix has been verified and will be deployed to production in 15 minutes.
- monitoring Aug 26, 2026, 11:04 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 26, 2026, 11:51 AM UTC
This incident has been resolved.
- postmortem Aug 28, 2026, 09:47 AM UTC
In 11.0.9.version we released an improvement for memory handling to be able to scale workload in a more efficient way. This was tested in our test environments but no issues were found. After releasing 11.0.9. we monitored the solution and noticed that the application servers were not performing as expected and processes were taking too long to complete and were timing out. Very soon we concluded on the root cause and decided to release a patch version which fixed the issue. We will add a mechanism to prevent processes to run too long on the servers and to prevent integrations to trigger the same process again in case we have a similar issue. This will stop the problem from escalating. We have also agreed on a process that should be followed with similar changes so that we are more aware of the risk and are able to notice it earlier in the development process.