Visma had 139 outages in the last 2 years totaling 49h 58m of downtime — averaging 5.7 incidents per month.
There were 139 Visma outages since February 6, 2026 totaling 49h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.
Dashboard is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Dashboard has been resolved. We will keep monitoring to ensure everything remains stable.
Banking is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Banking has been resolved. We will keep monitoring to ensure everything remains stable.
We are experiencing issues in Maventa that have been causing: Delays in invoice sending: up to 12 hours + more for a small amount of invoices Missing acks to Finnish operators Missing or delayed delivery statuses Issue has been identified and is being fixed.
A fix has been implemented and the issues have stopped 2026-10-12 10:45 EEST.
Meg is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Meg has been resolved. We will keep monitoring to ensure everything remains stable.
We had an issue in Business NXT today. The service (both the application and API) was down for 8 minutes between 10:02 and 10:10 Norwegian time. The issue is now resolved and the service is up and running as normal. We will continue monitoring to ensure stable operation.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified an issue with Payment service in Visma Net that is causing slowness in processing payments and payment statuses. We are working on a fix.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
The issue has now been fixed and we are monitoring.
We are continuing to monitor for any further issues.
The monitoring shows that everything is back to normal now
During infrastructure scaling operation this morning for some reason one database become unavailable. Cloud provider is working on bringing it back online.
We are continuing to work on a fix for this issue.
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 is being implemented.
A fix has been implemented and we are monitoring the results.
We have found a second issue impacting the performance. We are currently working on a fix. This is impacting creating outgoing payments from Process payments screen. Until the fix it is not possible to send outgoing payments from Visma Net. Estimated time for deploying fix is around 1 hour (13 CET).
We have an issue with access to one database after we scaled up our infrastructure during the slow performance. We are working together with the Cloud provider to restore the connection. Customers using this database are not able to access their company at the moment.
A fix has been implemented and we are monitoring. All payments that were stuck will be handled automatically. Due to high load, this might take a while. It is now also possible to sed new payments from Visma Net.
We are continuing to monitor for any further issues.
This incident has been resolved.
Payment is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Payment has been resolved. We will keep monitoring to ensure everything remains stable.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Strādājam pie risinājuma
A fix has been implemented and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Slow performance on Visma Online. Some users can experience white page when trying to login to Spiris
This incident has been resolved
We are currently investigating an issue in Financial Overview.
The issue appears to be specific to Chrome. As a workaround, use Firefox or Safari.
We have done a re-deploy and the application is up and running.
This incident has been resolved.
Condition: Automatic processing of uploaded documents in the Flyt AI API was unavailable, and audio summaries were slower than normal. Transcription was not affected. Timeline: Started 29 Sep 2026, 12:05 CEST. Resolved 15:24 CEST. Actions: The incident was caused by an outage at our cloud provider. We moved document processing to a backup location, and documents have been processed normally since 15:24 CEST. Documents submitted during the incident need to be resubmitted.
An outage at our cloud provider made automatic document processing in the Flyt AI API unavailable on 29 September between 12:05 and 15:24 CEST. We restored service by moving processing to a backup location, and have since made failover between locations automatic so a similar outage has less impact.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
Interco is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Interco has been resolved. We will keep monitoring to ensure everything remains stable.
Marketplace is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Marketplace has been resolved. We will keep monitoring to ensure everything remains stable.
Integretionmicrosoft365 is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Integretionmicrosoft365 has been resolved. We will keep monitoring to ensure everything remains stable.
Archive is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Archive has been resolved. We will keep monitoring to ensure everything remains stable.
Stability is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Stability has been resolved. We will keep monitoring to ensure everything remains stable.
Research is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Research has been resolved. We will keep monitoring to ensure everything remains stable.
Thirdpartyreference is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Thirdpartyreference has been resolved. We will keep monitoring to ensure everything remains stable.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
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 the results.
This incident has been resolved.
Inqom Api is currently experiencing a major outage. Our team is investigating the issue.
The incident affecting Inqom Api has been resolved. We will keep monitoring to ensure everything remains stable.