Visma Nmbrs experienced a major incident on January 19, 2026 affecting Web Application (APM) and Web Application (APM) and 1 more component, lasting 2d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 19, 2026, 08:55 AM UTC
We have received a notion of slowness in our application. We are investigating the root cause of this matter and will update this incident as soon as possible
- identified Jan 19, 2026, 09:11 AM UTC
The issue has been identified and a fix is being implemented.
- identified Jan 19, 2026, 11:31 AM UTC
The root cause is currently being investigated, and we are working on identifying a solution.
- identified Jan 19, 2026, 03:56 PM UTC
We believe we have found the cause of the problem. Tonight at 8:00 PM CET, we will be performing an update that should potentially resolve this issue. The update will have no impact on Nmbrs accessibility. We are closely monitoring the situation and will update you on the outcome.
- monitoring Jan 19, 2026, 07:24 PM UTC
A fix has just been implemented, and we will continue to monitor the situation closely in the coming period.
- investigating Jan 20, 2026, 08:45 AM UTC
Unfortunately, the previous fix did not resolve the issue. We are continuing our investigation and hope to provide a solution soon.
- investigating Jan 20, 2026, 09:49 AM UTC
The issue is still under investigation.
- investigating Jan 20, 2026, 10:32 AM UTC
We are continuing to investigate this issue.
- investigating Jan 20, 2026, 11:03 AM UTC
We will provide an update every 30 minutes via the status page. The issue related to availability has been identified. The investigation into the performance is still ongoing.
- investigating Jan 20, 2026, 11:30 AM UTC
A reboot has been performed, and we are monitoring its effects. The performance is still degraded, and the root cause is still under investigation.
- investigating Jan 20, 2026, 12:07 PM UTC
An improvement has been implemented, this had a noticeably positive effect. We will continue monitoring.
- investigating Jan 20, 2026, 12:56 PM UTC
The overall performance has improved but is still not optimal. The investigation remains ongoing.
- investigating Jan 20, 2026, 01:30 PM UTC
From now on, we will provide an update every hour. The investigation is still ongoing.
- investigating Jan 20, 2026, 02:30 PM UTC
We are continuing to investigate the issue.
- investigating Jan 20, 2026, 03:58 PM UTC
Response times have noticeably improved, but they are still not yet optimal. For this reason, an additional update will be performed tonight at 22:00 to further reduce the load on the system. We will monitor the results afterwards.
- monitoring Jan 20, 2026, 10:54 PM UTC
The update has been completed and an improvement has been implemented. We will continue to monitor the results and provide a new update tomorrow morning.
- monitoring Jan 21, 2026, 08:40 AM UTC
The results so far are positive, with significantly improved response times. We will continue to monitor the system and will share further updates as needed.
- resolved Jan 21, 2026, 10:17 AM UTC
The system is performing as expected. Response times remain stable and fast. We will close this incident, but will continue to monitor the situation.