Visma had 87 outages in the last 2 years totaling 430h 8m of downtime — averaging 3.6 incidents per month.
There were 87 Visma outages since February 6, 2026 totaling 430h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.
Due to a change in configuration and a cached instance our portal (Inyett One) lost communication with one of our backend resources. This was remediated by recreating the instances for the app service that was holding the cached value.
sortering i kurskatalog er feil. Mulig å gjennomføre kurs og søke etter kurs i katalogen. Feilen er lokalisert og under retting.
Feilen er rettet.
We are currently investigating an issue in Spiris Accounting, Invoicing & Payroll, Visma eAccounting, and Visma Administration. At the moment, it is not possible to send e-invoices. We are investigating the issue.
We are still investigating the issue preventing e-invoices from being sent. It is still possible We will update you again as soon as we have any new information.
We are working to resolve the issue as quickly as possible. We will update you again as soon as we have new information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue in Approval login
We are working on a fix. For the moment Connect login was disabled in production.
Some features like the Gaia assistant stop working until the fix will be implemented.
The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue in Visma Recruit.
In Swedish; Vi har identifierat orsaken till incidenten, som är kopplad till dagens release. Vi arbetar för närvarande med att ta fram en lösning och återkommer med en ny statusuppdatering så snart vi har mer information. Vi beklagar besväret. In English; We have identified the cause of the incident, which is related to today's release. We are currently working on a solution and will provide a status update as soon as we have more information. We apologize for the inconvenience
På svenska: Tjänsten är åter i full drift och problemet ska nu vara löst för samtliga kunder. Vi övervakar systemet noggrant under den närmaste tiden för att säkerställa stabil drift och hög kvalitet. In English: The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.
Driftstörningen är nu helt löst och Visma Recruit är i normal drift sedan klockan 19:00. Vi tackar för ert tålamod under tiden vi arbetade med att åtgärda felet! In English: The issue is now fully resolved and Visma Recruit has been running as normal since 19:00. Thank you for your patience while we worked to resolve this issue!
We are investigating issues with document downloads and degraded performance.
This incident has been resolved.
We are currently looking into performance degradation in Payroll.
We've deployed fixes to address the degraded performance and the service is now operating normally. We'll continue to monitor to confirm full resolution.
This incident has been resolved.
We are experiencing unusual slowness, we are investigating.
We are continuing to investigate this issue.
This incident has been resolved.
The issue has been identified.
This incident has been resolved.
We are currently investigating an issue in Business NXT API. Some mutations do not return a result even if they are executed successfully. Reading operations are working as expected. We will be back with more information shortly.
The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.
The issue is now resolved and the service is up and running as normal.
We're experiencing again slowness in all our Applications We're looking into the issue as we speak
High response time seems to be due to high load on a network shared resource we're using with other projects. Network team will undergo an emergency maintenance window to increase resources on that infrastructure in order to handle more load during red periods. Emergency Maintenance will happen soon, when everything will be settled time will as well be announced
Emergency change has been implemented, server resources seem to handle better the load, we're now monitoring the results and if all our infrastructure goes back to normal behaviour
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing problems in Maventa service, starting Friday 2026-05-29 14:00 UTC and still ongoing. The issues are causing: - Delays in importing incoming invoices and documents from Peppol - Delays in sending invoices - Timeouts on API (especially lookup methods) - Timeouts on Maventa UI Finder We are currently investigating these issues.
A fix has been implemented at 12:22 UTC and we are monitoring the situation
This incident has been resolved.
We have identified the cause of the incident and are currently working on finding a solution for this. The error blocks our Customer invoices flow. This impacts users of Inexchange and Hubix.
The service is up and running again for new invoices. This issue should be solved for all customers sending new Customer invoices. We will keep monitoring to ensure high quality.
We are continuing to monitor for any further issues.
The issue is now resolved and the service is up and running as normal.
We are currently investigating an issue in the old payroll ui. New Payroll UI is working as normal.
The issue has been identified, we are working on a fix.
A fix has been implemented. We are monitoring the situation.
This incident has been resolved.
Smartscan's purchase lines requests are experiencing longer processing times or timing out.
We are continuing to monitor for any further issues.
This incident has been resolved.
Smartscan customers may experience slower processing times due to a resource shortage
We are working on a solution.
Performance is back to normal. We will keep monitoring to ensure high quality.
The issue is now resolved and the service is up and running as normal.
We are currently investigating an issue in Visma.net Platform. VLSCore service, serving mostly OnPremise-Cloud integrations is under load.
The issue has been identified and a fix is implemented
2 more instances have been raised up and application seems to be able to cope with the load currently. We are monitoring this
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring that all is back to normal
This incident has been resolved.
Incident was caused by a failing maintenance operation that left one of our databases in an inconsistent state. We restored the data and were able to fix the problem. We agreed how to improve the process so that this can be avoided in the future
Downloading of invoices via rest api that were converted was unavailable during 16:08 and 17:30. There was no data loss, and automatically retried operations were succesfull after 17:30.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.