- Detected by Pingoru
- Apr 29, 2026, 03:07 PM UTC
- Resolved
- Apr 30, 2026, 09:30 AM UTC
- Duration
- 18h 23m
Affected: CS - Visma Directe bankkoppeling
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 03:04 PM UTC
- Resolved
- Apr 30, 2026, 09:31 AM UTC
- Duration
- 18h 27m
Affected: CS - AccountView.Net
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 08:43 PM UTC
- Resolved
- Apr 29, 2026, 01:57 PM UTC
- Duration
- 17h 14m
Affected: Visma NetVisma Net API
Timeline · 11 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 01:30 PM UTC
- Resolved
- Apr 28, 2026, 03:10 PM UTC
- Duration
- 1h 39m
Affected: Visma Net API
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 10:25 AM UTC
- Resolved
- Apr 27, 2026, 06:50 AM UTC
- Duration
- 2d 20h
Affected: Visma Flyt PPTVisma Flyt BVVVisma Flyt HelseVisma Flyt Sikker SakFlyt Barnevern
Timeline · 7 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 09:31 AM UTC
- Resolved
- Apr 24, 2026, 10:38 AM UTC
- Duration
- 1h 7m
Affected: CS - Visma Directe bankkoppeling
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 08:50 AM UTC
- Resolved
- Apr 24, 2026, 09:30 AM UTC
- Duration
- 40m
Affected: Spiris - Skatt & BokslutSpiris - Koncernredovisning
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 09:35 AM UTC
- Resolved
- Apr 10, 2026, 12:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 20, 2026, 09:35 AM UTC
Text in Test of Controls page not visible in Sticos Descartes
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 04:35 PM UTC
- Resolved
- Apr 16, 2026, 06:40 PM UTC
- Duration
- 2h 5m
Affected: CS - Visma.net AutoReport
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 01:00 PM UTC
- Resolved
- Apr 16, 2026, 01:50 PM UTC
- Duration
- 49m
Affected: Visma.net Payroll Norway
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 08:01 AM UTC
- Resolved
- Apr 16, 2026, 08:06 AM UTC
- Duration
- 4m
Affected: Visma.net Expense
Timeline · 2 updates
-
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
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 04:41 PM UTC
- Resolved
- Apr 15, 2026, 08:12 PM UTC
- Duration
- 3h 31m
Affected: Visma HorizonVisma HoPNumo
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 12:46 PM UTC
- Resolved
- Apr 14, 2026, 02:45 PM UTC
- Duration
- 1h 58m
Affected: GAiA Assistant
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 08:30 AM UTC
- Resolved
- Apr 14, 2026, 10:14 AM UTC
- Duration
- 1h 43m
Affected: Visma.net Calendar AbsenceVisma.net Calendar Time
Timeline · 3 updates
-
investigating Apr 14, 2026, 08:30 AM UTC
There is currently a delay in the Calendar. We have identified the cause of the incident and are currently working on finding a solution for this.
-
monitoring Apr 14, 2026, 09:17 AM UTC
The issue is fixed but there is still a delay in the system. We will keep monitoring to ensure a decrease of the delay.
-
resolved Apr 14, 2026, 10:14 AM UTC
The issue is now resolved and the service is up and running as normal.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 12:35 PM UTC
- Resolved
- Apr 13, 2026, 12:35 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 13, 2026, 12:35 PM UTC
Performance was degraded for 30 minutes starting at 13:28 CEST on 2026-04-13. We are aware of the issue and monitoring the situation, and we will be back with more information if the issue continues.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 11:02 AM UTC
- Resolved
- Apr 09, 2026, 12:37 PM UTC
- Duration
- 1h 35m
Affected: Visma NetVisma Net API
Timeline · 5 updates
-
investigating Apr 09, 2026, 11:02 AM UTC
We are investigating an issue together with cloud provider related to deploying new server nodes which fails randomly. This may cause degraded performance.
-
investigating Apr 09, 2026, 11:32 AM UTC
We are continuing to investigate this issue.
-
monitoring Apr 09, 2026, 12:15 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 09, 2026, 12:37 PM UTC
This incident has been resolved.
-
postmortem Apr 09, 2026, 12:38 PM UTC
Problem was caused by a capacity issue in the region we are located. We continue to work with the cloud provider to find a long term solution.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 10:59 AM UTC
- Resolved
- Apr 14, 2026, 12:53 PM UTC
- Duration
- 6d 1h
Affected: CS - Visma WebInvoice / Visma Webfaktura
Timeline · 3 updates
-
investigating Apr 08, 2026, 10:59 AM UTC
We have identified the root cause of the issue and are currently working on a fix. Our goal is to have the fix ready by the end of the day. Any unforeseen issues during testing or deployment may impact this timeline. We will keep you updated on our progress.
-
monitoring Apr 14, 2026, 07:41 AM UTC
Webfaktura synchronization is up and running again and this issue should be solved for all customers. We will keep monitoring to ensure high quality.
-
resolved Apr 14, 2026, 12:53 PM UTC
The issue is now resolved and the service is up and running as normal.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 11:51 AM UTC
- Resolved
- Apr 01, 2026, 02:04 PM UTC
- Duration
- 2h 12m
Timeline · 4 updates
-
investigating Apr 01, 2026, 11:51 AM UTC
We are currently investigating an issue regarding login to Approval. We will be back with more information shortly.
-
investigating Apr 01, 2026, 12:04 PM UTC
We are working on a fix. For the moment Connect login was disabled in production.
-
monitoring Apr 01, 2026, 12:31 PM UTC
The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.
-
resolved Apr 01, 2026, 02:04 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 06:45 AM UTC
- Resolved
- Apr 01, 2026, 06:04 PM UTC
- Duration
- 11h 19m
Affected: Enterprise Plus
Timeline · 3 updates
-
investigating Apr 01, 2026, 06:45 AM UTC
We have identified that we have hit some limits on the infrastructure part and we are working on fixing the issue which will allow our applications to start.
-
monitoring Apr 01, 2026, 08:23 AM UTC
We have identified the cause of the incident and we have implemented a solution. The services should be available shortly. This issue should be solved for all customers. We will keep monitoring to ensure the high quality of our services.
-
resolved Apr 01, 2026, 06:04 PM UTC
The issue is now resolved and the services are coming up and will be available shortly.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 08:26 AM UTC
- Resolved
- Apr 01, 2026, 05:31 AM UTC
- Duration
- 21h 4m
Affected: Maventa / Visma .net AutoInvoice
Timeline · 4 updates
-
investigating Mar 31, 2026, 08:26 AM UTC
We are currently investigating this issue.
-
identified Mar 31, 2026, 08:29 AM UTC
We have identified issues with delayed webhook deliveries.
-
monitoring Mar 31, 2026, 09:14 AM UTC
A fix has been implemented and we are monitoring the results. There are still delayed webhook events during the incident window that will need to be reprocessed to ensure delivery.
-
resolved Apr 01, 2026, 05:31 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 07:51 AM UTC
- Resolved
- Mar 31, 2026, 11:01 AM UTC
- Duration
- 3h 9m
Affected: Business NXT Provisioning and migration platform
Timeline · 3 updates
-
investigating Mar 31, 2026, 07:51 AM UTC
We are currently investigating an issue in the Business NXT migration service, preventing migrations to complete successfully. We will be back with more information shortly.
-
monitoring Mar 31, 2026, 10:01 AM UTC
The migration service is up and running again and the issue should be solved for all customers. We will keep monitoring to ensure high quality.
-
resolved Mar 31, 2026, 11:01 AM UTC
The issue is now resolved and the service is up and running as normal.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 07:37 AM UTC
- Resolved
- Mar 31, 2026, 01:44 PM UTC
- Duration
- 6h 6m
Affected: Enterprise Plus
Timeline · 4 updates
-
investigating Mar 31, 2026, 07:37 AM UTC
We are working to identify the challenges and will inform you as soon as we have found and resolved the problem.
-
investigating Mar 31, 2026, 11:06 AM UTC
We have identified the cause of the incident and are currently working on finding a solution for this. The services responsible for login are up but we see that some of our services are still not starting. We are working on having them up as well.
-
investigating Mar 31, 2026, 11:06 AM UTC
We have identified the cause of the incident and are currently working on finding a solution for this. The services responsible for login are up but we see that some of our services are still not starting. We are working on having them up as well.
-
resolved Mar 31, 2026, 01:44 PM UTC
The issue is now resolved and the service is up and running as normal.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 03:09 PM UTC
- Resolved
- Mar 27, 2026, 08:26 PM UTC
- Duration
- 5h 17m
Affected: Enterprise Plus
Timeline · 5 updates
-
investigating Mar 27, 2026, 03:09 PM UTC
We have an issue in Enterprise Plus that is affecting some modules. we are working on identifying the root cause
-
investigating Mar 27, 2026, 03:10 PM UTC
We are currently in contact with AWS support to identify the root cause of this incident.
-
investigating Mar 27, 2026, 07:40 PM UTC
We have identified the cause of the incident and we have implemented a solution for this. The services will be up again shortly.
-
monitoring Mar 27, 2026, 08:12 PM UTC
The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.
-
resolved Mar 27, 2026, 08:26 PM UTC
The issue is now resolved and the service is up and running as normal.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 01:27 PM UTC
- Resolved
- Mar 27, 2026, 02:09 PM UTC
- Duration
- 41m
Affected: Enterprise Plus
Timeline · 3 updates
-
investigating Mar 27, 2026, 01:27 PM UTC
We are currently investigating this issue
-
monitoring Mar 27, 2026, 01:54 PM UTC
A fix has been implemented an we are monitoring the situation
-
resolved Mar 27, 2026, 02:09 PM UTC
This incident has been resolved
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 09:41 AM UTC
- Resolved
- Mar 26, 2026, 02:46 PM UTC
- Duration
- 5h 5m
Affected: Business NXT ERP
Timeline · 3 updates
-
investigating Mar 26, 2026, 09:41 AM UTC
We are currently investigating an issue in Business NXT. Some customers experience problems when sending VAT reports to AutoReport, where response messages from AutoReport are not handled correctly. Potential consequences are that batch and vouchers are not updated correctly. Our advice is for the customers not to send VAT reports until we have fixed this, if possible. We will be back with more information shortly.
-
monitoring Mar 26, 2026, 01:08 PM UTC
This issue should be solved for all customers, and it's ok for customers to send VAT reports again. We apologize for the inconvenience. We will keep monitoring to ensure high quality.
-
resolved Mar 26, 2026, 02:46 PM UTC
The issue is now resolved.
Read the full incident report →
