Visma Nmbrs had 13 outages in the last 2 years totaling 239h 7m of downtime — averaging 0.5 incidents per month.
There were 13 Visma Nmbrs outages since May 19, 2025 totaling 239h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Currently we are still investigating the situation.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
To resolve the issue, we have restarted a number of services. We are currently monitoring the impact of this action and will continue to do so to ensure system stability.
A fix has been implemented and we are monitoring the results.
Downloading the payslips and processing the run is now possible again. At the moment, downloading documents to PDF still results in an error. The cause of this issue is currently under investigation.
A fix has been implemented, restoring the ability to download documents as PDF. We are currently monitoring the results.
The live environment functions have been fully restored. We keep on monitoring the results. In some sandbox environments, the same error messages may still appear, but these will be resolved overnight through a restore.
This incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
The root cause is still under investigation. At this moment, activating a new integration and synchronizing new data is not possible for the Plus features.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have received a notion of slowness and the inability to log in in our application. We are investigating the root cause of this matter and will update this incident as soon as possible
This incident has been resolved.
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
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
We will perform an etra update tonight to combat the overall slowness experienced in the application.
Nmbrs is currently experiencing performance issues due to a problem with Microsoft Azure. This may result in slower loading times, pages failing to load, or pages being displayed incorrectly.
Microsoft has also published a status page regarding this issue, which can be found here: https://azure.status.microsoft/en-us/status
Due to the microsoft outage we decided to put Nmbrs offline
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix will be implemented with the Sandbox reset tonight.
Unfortunately, the previous fix did not resolve the issue. We have restarted our investigation and are working to identify the root cause.
The issue has been identified and a fix will be implemented during this weekend.
Unfortunately, the previous solutions did not fully resolve the issue. We have resumed our investigation to identify the underlying cause and are working on a permanent fix.
We've identified the issue and a fix will be implemented. We'll keep you updated on the progress.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have received a notion of slowness and certain pages are not displaying correctly. We are investigating the root cause of this matter and will update this incident as soon as possible
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
It is not possible to log in when 2FA is needed. This is being investigated with high priority
We’ve identified a potential solution to the issue and are currently conducting further testing to confirm its effectiveness. Our team is closely monitoring the situation and will provide updates here as soon as we have more information or when the fix has been fully implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The sandbox can not be reached at this moment. The cause is currently being investigated.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.