Visma Outage History
Visma major outage View live status →Pingoru has recorded 188 incidents for Visma: 188 in the last 12 months and 92 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 19 | 280 of 720 (39%) |
| May 2026 | 18 | 62 of 744 (8%) |
| June 2026 | 18 | 301 of 720 (42%) |
| July 2026 | 14 | 30 of 744 (4%) |
| August 2026 | 44 | 137 of 744 (18%) |
| September 2026 | 20 | 19 of 720 (3%) |
| October 2026 | 17 | 130 of 591 (22%) |
Incidents, newest first
Major May 21, 2026 Investigating an issue in Visma.net Platform - VLSCore 1h 14m Visma.net ODP
Started May 21, 2026, 05:43 AM UTC· resolved May 21, 2026, 06:57 AM UTC
- investigating May 21, 2026, 05:43 AM UTC
We are currently investigating an issue in Visma.net Platform. VLSCore service, serving mostly OnPremise-Cloud integrations is under load.
- identified May 21, 2026, 06:19 AM UTC
The issue has been identified and a fix is implemented
- monitoring May 21, 2026, 06:36 AM UTC
2 more instances have been raised up and application seems to be able to cope with the load currently. We are monitoring this
- resolved May 21, 2026, 06:57 AM UTC
This incident has been resolved.
Major May 19, 2026 Smartscan degraded performance –
Started May 19, 2026, 07:30 AM UTC· resolved May 19, 2026, 07:30 AM UTC
- resolved May 21, 2026, 10:01 AM UTC
Smartscan customers may experience slower processing times due to a resource shortage
Critical May 16, 2026 Problems with login in Visma net 49m Visma Net, Visma Net API
Started May 16, 2026, 05:24 AM UTC· resolved May 16, 2026, 06:14 AM UTC
- investigating May 16, 2026, 05:24 AM UTC
We are currently investigating this issue.
- investigating May 16, 2026, 05:48 AM UTC
We are continuing to investigate this issue.
- monitoring May 16, 2026, 06:09 AM UTC
A fix has been implemented and we are monitoring that all is back to normal
- resolved May 16, 2026, 06:14 AM UTC
This incident has been resolved.
- postmortem May 22, 2026, 01:46 PM UTC
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
Major May 12, 2026 Approval failing requests 5m CS - Visma.net Approval
Started May 12, 2026, 06:38 AM UTC· resolved May 12, 2026, 06:44 AM UTC
- investigating May 12, 2026, 06:38 AM UTC
We are currently investigating this issue.
- monitoring May 12, 2026, 06:40 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 12, 2026, 06:44 AM UTC
This incident has been resolved.
Major May 12, 2026 Invoice conversion unavailable –
Started May 12, 2026, 01:30 AM UTC· resolved May 12, 2026, 01:30 AM UTC
- resolved May 14, 2026, 06:28 AM UTC
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.
Minor May 11, 2026 Slowness in Visma.net Payroll 9h 21m Visma.net Payroll Norway
Started May 11, 2026, 11:15 AM UTC· resolved May 11, 2026, 08:36 PM UTC
- investigating May 11, 2026, 11:15 AM UTC
We are currently investigation an issue causing slowness in Visma.net Payroll
- monitoring May 11, 2026, 01:03 PM UTC
Performance is normal again, we continue to monitor the situation
- resolved May 11, 2026, 08:36 PM UTC
This incident has been resolved.
Notice May 11, 2026 Downgraded performance for some customers in Visma Net ERP 3h 21m Visma Net
Started May 11, 2026, 11:14 AM UTC· resolved May 11, 2026, 02:35 PM UTC
- identified May 11, 2026, 11:14 AM UTC
Some customers, belonging to the same server, are experiencing a slower performance. We have identified the problem. There is one customer that are making a lot of calls when trying to connect via API. We are reaching out to the customer.
- identified May 11, 2026, 12:42 PM UTC
We are now upscaling our resources for the server with lower performance.
- monitoring May 11, 2026, 01:00 PM UTC
Performance is normal again, we continue to monitor the situation
- resolved May 11, 2026, 02:35 PM UTC
This incident has been resolved.
- postmortem May 20, 2026, 09:24 AM UTC
Problem was caused by a query that was executed on one of our SQL servers. All customers that were on the same server were impacted by the slowness. We have now improved the functionality related to the query to prevent similar issue from happening in the future.
Minor May 11, 2026 Investigating an issue in Visma Net related to incoming invoices 2h 32m Visma Net
Started May 11, 2026, 08:32 AM UTC· resolved May 11, 2026, 11:05 AM UTC
- investigating May 11, 2026, 08:32 AM UTC
We are currently investigating an issue in Visma Net related to incoming invoices, not all invoices are arriving to Visma Net from AutoInvoice.
- investigating May 11, 2026, 10:21 AM UTC
We are continuing to investigate this issue.
- monitoring May 11, 2026, 10:22 AM UTC
Issue was identified and immediately fixed, we are now monitoring.
- resolved May 11, 2026, 11:05 AM UTC
The issue is fixed and we see that invoices are received in Visma Net ERP again.
- postmortem May 12, 2026, 10:51 AM UTC
The root cause was a scheduled task in our infrastructure getting stuck on Friday evening 8th May. This resulted in no invoices being delivered from AutoInvoice to Visma Net ERP. Monday morning 11th May we started receiving information about this, and after a short investigation we could identify the problem and solve it by manually restarting the scheduler task. To prevent this from happening in the future we have now changed the configuration to automatically restart if getting stuck. In addition we will create alerts to notify this proactively.
Notice May 6, 2026 Login problem for IM web and Control Edge 1h 22m Control Edge, Invoice Manager, Control Edge User Management
Started May 06, 2026, 09:01 AM UTC· resolved May 06, 2026, 10:23 AM UTC
- investigating May 06, 2026, 09:01 AM UTC
We are currently investigating this issue.
- investigating May 06, 2026, 09:02 AM UTC
We are continuing to investigate this issue.
- monitoring May 06, 2026, 09:45 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 06, 2026, 10:23 AM UTC
We are continuing to monitor for any further issues.
- resolved May 06, 2026, 10:23 AM UTC
This incident has been resolved.
- postmortem May 06, 2026, 10:24 AM UTC
Based on the following Notification from Microsoft: Warning Windows updates for CVE-2026-20833 enforce RC4 hardening in phases. Plan and complete remediation before full enforcement: * January 13, 2026 - Initial deployment phase:Updates introduce audit signals and preparation controls. * April 2026 - Enforcement phase \(manual rollback available\):Default Kerberos KDC behavior shifts to AES-first, and RC4-dependent scenarios can start failing unless explicitly configured. * July 2026 - Enforcement phase \(final\):Updates remove rollback support and keep enforcement enabled. we disabled the Kerberos RC4 encryption on the EntraID Domain Services. The configuration was leading to the mentioned incident. As this will be anyhow eminent to happen \( enforcement of Kerberos to AES \) we will continue internal investigation with Microsoft Support to identify root cause of the action applied today. Until further notice the Kerberos RC4 encryption will remain enabled.
Minor May 6, 2026 Investigating slow performance in Calendar 3h 14m Visma.net Calendar Absence, Visma.net Calendar Time, Visma.net Calendar Roster
Started May 06, 2026, 07:59 AM UTC· resolved May 06, 2026, 11:13 AM UTC
- investigating May 06, 2026, 07:59 AM UTC
We are currently investigating slow performance in Calendar
- monitoring May 06, 2026, 10:05 AM UTC
We are currently monitoring the performance.
- resolved May 06, 2026, 11:13 AM UTC
The issue is now resolved and the service is up and running as normal.
Major May 4, 2026 Pågående problem: Tilgang til startsiden og feil i Enterprise Plus 2h 24m Enterprise Plus
Started May 04, 2026, 09:13 AM UTC· resolved May 04, 2026, 11:37 AM UTC
- investigating May 04, 2026, 09:13 AM UTC
Norsk: Oppdatering om de tekniske utfordringene Status: Vi jobber fortsatt med å løse de siste problemene Vi ser at enkelte av dere dessverre fortsatt opplever utfordringer, blant annet med feilmeldinger som "Service Unavailable" og problemer med å hente oppgaver fra HRM (fakturaer og ebilag). Vi vil forsikre dere om at vi er fullt klar over situasjonen. Teamet vårt jobber ufortrødent videre med å finne og rette de gjenstående feilene slik at alt skal fungere som normalt for alle brukere. Vi beklager virkelig at dette tar tid og for ulempene dette skaper i arbeidsdagen deres. Vi kommer med ny informasjon så snart vi har en oppdatering. Takk for tålmodigheten! English: Update on technical issues Status: Work continues to resolve remaining issues We are aware that some users are unfortunately still experiencing issues, including "Service Unavailable" errors and difficulties retrieving tasks from HRM (such as invoices and e-vouchers). We want to assure you that we are fully aware of the situation. Our team is working continuously to identify and fix the remaining bugs so that everything returns to normal for all users. We sincerely apologize for the time this is taking and for the inconvenience this causes to your workday. We will provide more information as soon as we have an update. Thank you for your continued patience!
- resolved May 04, 2026, 11:37 AM UTC
Norsk: Statusoppdatering – Problemet er løst ✅ Løst: Systemene er tilbake i normal drift Vi er glade for å meddele at problemet med startsiden nå er løst. Vi har iverksatt tiltak som har gjenopprettet full tilgang for alle kunder. For å være helt på den sikre siden fortsetter vi å overvåke situasjonen tett utover. Samtidig gjennomfører vi noen ekstra utbedringer i systemet for å styrke stabiliteten og forhindre at lignende skjer igjen. Takk for at dere har vært tålmodige med oss – nå skal alt rulle som det skal! English: Status Update – Resolved ✅ Resolved: Systems are back to normal We are happy to report that the issue affecting the startpage has been resolved, and service is fully restored for all customers. We are currently monitoring the situation closely to ensure continued stability. In addition, we are implementing further improvements to the system to strengthen performance and prevent future occurrences. Thank you for your patience and for sticking with us!
Major May 4, 2026 Startpage Connectivity with issues 1h 34m Enterprise Plus
Started May 04, 2026, 07:12 AM UTC· resolved May 04, 2026, 08:46 AM UTC
- investigating May 04, 2026, 07:12 AM UTC
We are currently experiencing some technical challenges affecting the Startpage for some of our customers. Our engineering team is actively investigating to identify the root cause. We apologize for any inconvenience this may cause and will provide further updates as soon as more information is available. Thank you for your patience.
- investigating May 04, 2026, 07:17 AM UTC
Pågående problem: Tilgang til startsiden Vi opplever for øyeblikket tekniske utfordringer som påvirker startsiden for enkelte av våre kunder. Våre teknikere jobber aktivt med å identifisere rotårsaken til problemet. Vi beklager ulempene dette medfører, og vil komme med nye oppdateringer så snart vi har mer informasjon. Takk for tålmodigheten.
- investigating May 04, 2026, 07:22 AM UTC
Norsk: Oppdatering på situasjonen Oppdatering: Rotårsak funnet Vi har nå identifisert rotårsaken til utfordringene med startsiden. Teamet vårt holder for øyeblikket på med å rulle ut en rettelse (fix) for å løse problemet. Vi forventer at tjenesten vil fungere som normalt igjen om kort tid. Vi gir dere en siste bekreftelse så snart alt er verifisert. Takk for tålmodigheten mens vi har jobbet med dette! English: Status Update Update: Root Cause Identified We have identified the root cause of the issues affecting the startpage. Our team is currently deploying a fix to resolve the situation. We expect services to return to normal shortly and will provide a final confirmation once everything is fully verified. Thank you for your continued patience!
- monitoring May 04, 2026, 08:19 AM UTC
Oppdatering: Rettelse implementert – vi overvåker situasjonen Vi har nå implementert en rettelse for problemene med startsiden, og alt skal fungere som normalt igjen. Vi følger nøye med på systemene våre utover for å sikre at stabiliteten opprettholdes. Takk for at dere har vært så tålmodige med oss i dag! Skulle du mot formodning fortsatt oppleve problemer, kan det hjelpe å laste siden på nytt (Refresh). English: Status Update Update: Fix Implemented & Monitoring The fix for the homepage issue has now been successfully implemented. We are closely monitoring the situation to ensure everything remains stable and performs as expected. Thank you for hanging in there with us! If you still experience any issues, please try refreshing your browser.
- resolved May 04, 2026, 08:46 AM UTC
Norsk: Statusoppdatering – Problemet er løst ✅ Løst: Systemene er tilbake i normal drift Vi er glade for å meddele at problemet med startsiden nå er løst. Vi har iverksatt tiltak som har gjenopprettet full tilgang for alle kunder. For å være helt på den sikre siden fortsetter vi å overvåke situasjonen tett utover. Samtidig gjennomfører vi noen ekstra utbedringer i systemet for å styrke stabiliteten og forhindre at lignende skjer igjen. Takk for at dere har vært tålmodige med oss – nå skal alt rulle som det skal! English: Status Update – Resolved ✅ Resolved: Systems are back to normal We are happy to report that the issue affecting the startpage has been resolved, and service is fully restored for all customers. We are currently monitoring the situation closely to ensure continued stability. In addition, we are implementing further improvements to the system to strengthen performance and prevent future occurrences. Thank you for your patience and for sticking with us!
Major May 4, 2026 Smartscan slow processing times –
Started May 04, 2026, 07:00 AM UTC· resolved May 04, 2026, 07:00 AM UTC
- resolved May 04, 2026, 07:47 AM UTC
Smartscan experiencing slow processing times due to lack of resources available
Minor April 29, 2026 Investigating an issue in Visma Directe Bankkoppeling 18h 23m CS - Visma Directe bankkoppeling
Started Apr 29, 2026, 03:07 PM UTC· resolved Apr 30, 2026, 09:30 AM UTC
- identified Apr 29, 2026, 03:07 PM UTC
We are currently experiencing issues while retrieving data from the Chamber of Commerce. Customer who try to connect bank accounts of PSD2-connections will notice errors about the Chamber of Commerce being unavailable. There is no impact to any of the already connected bank accounts. We are working with the Chamber of Commerce to resolve the problem
- resolved Apr 30, 2026, 09:30 AM UTC
This incident has been resolved.
Minor April 29, 2026 Investigating an issue in AccountView.Net 18h 27m CS - AccountView.Net
Started Apr 29, 2026, 03:04 PM UTC· resolved Apr 30, 2026, 09:31 AM UTC
- identified Apr 29, 2026, 03:04 PM UTC
Customers trying to search in the Chamber of Commerce will notice errors. We are working with the Chamber of Commerce to resolve the problem
- resolved Apr 30, 2026, 09:31 AM UTC
The issue is now resolved and the service is up and running as normal.
Minor April 28, 2026 Degraded performance in Visma net 17h 14m Visma Net, Visma Net API
Started Apr 28, 2026, 08:43 PM UTC· resolved Apr 29, 2026, 01:57 PM UTC
- investigating Apr 28, 2026, 08:43 PM UTC
We are currently investigating this issue.
- monitoring Apr 29, 2026, 02:34 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 29, 2026, 05:21 AM UTC
We are continuing to monitor for any further issues.
- monitoring Apr 29, 2026, 06:41 AM UTC
We are continuing to monitor for any further issues.
- investigating Apr 29, 2026, 07:17 AM UTC
We are currently investigating this issue.
- identified Apr 29, 2026, 08:02 AM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 29, 2026, 09:11 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Apr 29, 2026, 10:07 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 29, 2026, 10:39 AM UTC
We are continuing to monitor for any further issues.
- resolved Apr 29, 2026, 01:57 PM UTC
This incident has been resolved.
- postmortem Apr 30, 2026, 12:47 PM UTC
Root cause was a change 10.94.0 related to authentication change where we wanted to optimize the flow of getting authentication tokens from Connect. The goal was to lower the amount of token requests towards Connect and therefore the risk of being throttled. Unfortunately the change led to a locking of threads on some application servers which caused timeouts and degraded performance for some of our customers. We were able to mitigate the problem with a patch by rolling back the change. Monitoring showed that we are back to normal again.
Minor April 28, 2026 Degraded performance on API 1h 39m Visma Net API
Started Apr 28, 2026, 01:30 PM UTC· resolved Apr 28, 2026, 03:10 PM UTC
- investigating Apr 28, 2026, 01:30 PM UTC
We are currently investigating this issue.
- identified Apr 28, 2026, 02:11 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 28, 2026, 03:10 PM UTC
This incident has been resolved.
- postmortem Apr 30, 2026, 01:03 PM UTC
Root cause was a change 10.94.0 related to authentication change where we wanted to optimize the flow of getting authentication tokens from Connect. The goal was to lower the amount of token requests towards Connect and therefore the risk of being throttled. Unfortunately the change led to a locking of threads on some application servers which caused timeouts and degraded performance for some of our customers. We were able to mitigate the problem with a patch by rolling back the change. Monitoring showed that we are back to normal again.
Major April 24, 2026 Flyt Common solutions having performance issues 2d 20h Flyt PPT, Flyt Barnevernvakt, Flyt Helse, Flyt Sikker Sak and 1 more
Started Apr 24, 2026, 10:25 AM UTC· resolved Apr 27, 2026, 06:50 AM UTC
- investigating Apr 24, 2026, 10:25 AM UTC
We are experiencing performance problems and errors. We are investigating
- investigating Apr 24, 2026, 10:29 AM UTC
We are continuing to investigate this issue.
- identified Apr 24, 2026, 11:23 AM UTC
We might have encounter what the root cause is, we're looking for possibilities how to resolve it right now
- identified Apr 24, 2026, 11:50 AM UTC
We're going to make an Emergency Change today at 15:00 NO time in order to resolve the degraded performance of all Flyt Common Applications. There is still on-going discussion of how change will be implemented. For now, the change will cause a downtime of ~30minutes on all FLYT Applications
- identified Apr 24, 2026, 01:06 PM UTC
The fix is going to implemented. The fix will generate a total downtime of less than 5 minutes and emergency maintenance will be done in about 30 minutes, ending at around 15:30.
- monitoring Apr 24, 2026, 01:29 PM UTC
Change has been implemented, we're monitoring the results
- resolved Apr 27, 2026, 06:50 AM UTC
This incident has been resolved.
Minor April 24, 2026 Issue submitting (bulk) payments to the rabobank via Visma Directe bankkoppeling 1h 7m CS - Visma Directe bankkoppeling
Started Apr 24, 2026, 09:31 AM UTC· resolved Apr 24, 2026, 10:38 AM UTC
- identified Apr 24, 2026, 09:31 AM UTC
Since 8:43 we are seeing errors when sending (bulk) payments to the Rabobank. The bank is aware of the issues and is working to resolve the issue. We will post an update when the status changes.
- resolved Apr 24, 2026, 10:38 AM UTC
The rabobank has fixed the issue which lasted from 24/04/2026 08:30 to 24/04/2026 12:05. The issue is now resolved and the service is up and running as normal.
Major April 24, 2026 Problems reaching some parts of our service 40m Spiris - Skatt & Bokslut, Spiris - Koncernredovisning
Started Apr 24, 2026, 08:50 AM UTC· resolved Apr 24, 2026, 09:30 AM UTC
- investigating Apr 24, 2026, 08:50 AM UTC
Right now we are experiencing problems reaching period closing and year-end closing in our service
- resolved Apr 24, 2026, 09:30 AM UTC
This incident has been resolved.
Minor April 16, 2026 AutoReport degraded performance 2h 5m CS - Visma.net AutoReport
Started Apr 16, 2026, 04:35 PM UTC· resolved Apr 16, 2026, 06:40 PM UTC
- investigating Apr 16, 2026, 04:35 PM UTC
AutoReport is experiencing degraded performance. We are investigating the issue.
- identified Apr 16, 2026, 04:56 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 16, 2026, 05:33 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 16, 2026, 06:40 PM UTC
This incident has been resolved.
Major April 16, 2026 Visma.net Payroll Partial outage 49m Visma.net Payroll Norway
Started Apr 16, 2026, 01:00 PM UTC· resolved Apr 16, 2026, 01:50 PM UTC
- investigating Apr 16, 2026, 01:00 PM UTC
We are currently investigating the incident
- identified Apr 16, 2026, 01:38 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 16, 2026, 01:50 PM UTC
This incident has been resolved.
Major April 16, 2026 Issue with register claims in Expense 4m Visma.net Expense
Started Apr 16, 2026, 08:01 AM UTC· resolved Apr 16, 2026, 08:06 AM UTC
- investigating Apr 16, 2026, 08:01 AM UTC
We are investigating an issue that it is not possible to register claims in Expense
- resolved Apr 16, 2026, 08:06 AM UTC
The issue has now been resolved and it is possible to register claims again
Minor April 15, 2026 Visma Horizon email sending issues 3h 31m Visma Horizon, Visma HoP, Numo
Started Apr 15, 2026, 04:41 PM UTC· resolved Apr 15, 2026, 08:12 PM UTC
- identified Apr 15, 2026, 04:41 PM UTC
We are having issues with outgoing emails from Visma Horizon, Visma HoP and Numo. We are identified the cause and working on the solution. Šobrīd nav iespējams izsūtīt e-pastus no Visma Horizon, Visma HoP and Numo. Problēmas cēlonis ir identificēts un mēs strādājam pie risinājuma.
- resolved Apr 15, 2026, 08:12 PM UTC
E-mail sending functionality is restored. E-pastu izsūtīšana ir atjaunota.
Critical April 14, 2026 GAiA Assistant chat not working 1h 58m GAiA Assistant
Started Apr 14, 2026, 12:46 PM UTC· resolved Apr 14, 2026, 02:45 PM UTC
- investigating Apr 14, 2026, 12:52 PM UTC
We are currently investigating this issue
- investigating Apr 14, 2026, 12:58 PM UTC
Working but still being investigated.
- identified Apr 14, 2026, 02:16 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 15, 2026, 06:13 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 15, 2026, 06:58 AM UTC
This incident has been resolved.