- Detected by Pingoru
- Mar 25, 2026, 01:21 PM UTC
- Resolved
- Mar 25, 2026, 01:21 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 25, 2026, 01:21 PM UTC
During release, GKE was out of GPU resources
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 06:20 AM UTC
- Resolved
- Mar 25, 2026, 11:42 AM UTC
- Duration
- 5h 21m
Affected: Visma Net
Timeline · 5 updates
-
investigating Mar 25, 2026, 06:20 AM UTC
We are currently investigating this issue.
-
identified Mar 25, 2026, 08:27 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 25, 2026, 09:04 AM UTC
A fix has been implemented and we are monitoring the status. In case users experience issues with 1008 version related to login they should clear cookies and logout and login again.
-
monitoring Mar 25, 2026, 11:41 AM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 25, 2026, 11:42 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 04:13 PM UTC
- Resolved
- Mar 24, 2026, 06:21 PM UTC
- Duration
- 2h 7m
Affected: Timetable Construction
Timeline · 3 updates
-
investigating Mar 24, 2026, 04:13 PM UTC
Timetable Construction validations not working. We are investigating the issue.
-
identified Mar 24, 2026, 04:14 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Mar 24, 2026, 06:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 10:52 AM UTC
- Resolved
- Mar 25, 2026, 05:26 AM UTC
- Duration
- 18h 33m
Affected: Visma Net
Timeline · 6 updates
-
investigating Mar 24, 2026, 10:52 AM UTC
We are currently investigating this issue.
-
investigating Mar 24, 2026, 11:24 AM UTC
We are continuing to investigate this issue.
-
investigating Mar 24, 2026, 12:47 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 24, 2026, 01:55 PM UTC
We are continuing to investigate this issue.
-
monitoring Mar 24, 2026, 03:42 PM UTC
We released a hotfix to stabilize login process. We continue to monitor the application.
-
resolved Mar 25, 2026, 05:26 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 08:47 AM UTC
- Resolved
- Mar 24, 2026, 09:29 AM UTC
- Duration
- 42m
Affected: Visma Net
Timeline · 3 updates
-
investigating Mar 24, 2026, 08:47 AM UTC
We are currently investigating this issue.
-
monitoring Mar 24, 2026, 09:13 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 24, 2026, 09:29 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 22, 2026, 12:45 PM UTC
- Resolved
- Mar 23, 2026, 07:09 AM UTC
- Duration
- 18h 23m
Affected: Visma Flyt PPTVisma Flyt BVVVisma Flyt HelseVisma Flyt Sikker SakVisma Flyt ArkivFlyt Barnevern
Timeline · 5 updates
-
investigating Mar 22, 2026, 01:50 PM UTC
Flyt Common solutions unavailable - This is due to a network issue.
-
identified Mar 22, 2026, 01:51 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Mar 22, 2026, 01:53 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Mar 22, 2026, 03:35 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 23, 2026, 07:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 12:12 PM UTC
- Resolved
- Mar 20, 2026, 02:12 PM UTC
- Duration
- 2h
Affected: Visma HoP
Timeline · 2 updates
-
investigating Mar 20, 2026, 12:12 PM UTC
Pašlaik saskaramies ar Visma Paraksts problēmām. Strādājam pie risinājuma. We are having issues with Visma Signature right now. Working on it
-
resolved Mar 20, 2026, 02:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 11:05 AM UTC
- Resolved
- Mar 19, 2026, 03:01 PM UTC
- Duration
- 3h 56m
Affected: Visma Net
Timeline · 6 updates
-
investigating Mar 19, 2026, 11:05 AM UTC
We are currently investigating this issue.
-
investigating Mar 19, 2026, 11:38 AM UTC
We are continuing to investigate this issue.
-
identified Mar 19, 2026, 12:04 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Mar 19, 2026, 12:15 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Mar 19, 2026, 01:02 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 19, 2026, 03:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 08:44 AM UTC
- Resolved
- Mar 23, 2026, 02:14 PM UTC
- Duration
- 4d 5h
Affected: HRM Analytics
Timeline · 6 updates
-
investigating Mar 19, 2026, 08:44 AM UTC
Unfortunately we are experiencing problems in our generic API which leads to time-outs at our customers.
-
investigating Mar 19, 2026, 01:22 PM UTC
We are still investigating the problem. The problem is likely in the datawarehouse delivering the data. Amazon Redshift is assisting us in finding the root cause. We expect the next update at 13.00 hrs.
-
investigating Mar 19, 2026, 05:06 PM UTC
API jobs are at the moment processed. We are still investigating an issue with refresh of the data used by the reports.
-
investigating Mar 19, 2026, 05:21 PM UTC
We are continuing to investigate this issue.
-
monitoring Mar 20, 2026, 08:51 AM UTC
The API is up and running. We are now starting refresh of the reporting data and monitoring the system behavior.
-
resolved Mar 23, 2026, 02:14 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 17, 2026, 03:40 PM UTC
- Resolved
- Mar 27, 2026, 02:01 PM UTC
- Duration
- 9d 22h
Affected: Spiris - Skatt & Bokslut
Timeline · 9 updates
-
identified Mar 17, 2026, 03:40 PM UTC
The issue has been identified. We will update with new information on an ongoing basis.
-
identified Mar 18, 2026, 10:39 AM UTC
We are working on a solution and will update when we have new information.
-
identified Mar 18, 2026, 03:06 PM UTC
We continue to work on a solution. As soon as we have an update or when it's solved we will give an update.
-
identified Mar 19, 2026, 12:52 PM UTC
The problem with some customers not being able to access their company is still not solved. When trying to log in on the companies with problem you get a message saying that the company is in maintenance. We continue to work on a solution.
-
identified Mar 20, 2026, 12:13 PM UTC
We are still working on a solution and will get back with an update on Monday.
-
identified Mar 24, 2026, 01:45 PM UTC
The issue with some customers not being able to access their company in Skatt & Bokslut is still not solved. We do our best to solve the problem as quick as possible. As soon as it's solved we will inform on Statuspage.
-
identified Mar 26, 2026, 10:34 AM UTC
Solution of the problem is now in progress and this will lead to less and less impact of the problem. Will get back with an update as soon as there is new information to share.
-
monitoring Mar 27, 2026, 12:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 27, 2026, 02:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 07:34 AM UTC
- Resolved
- Mar 17, 2026, 08:07 AM UTC
- Duration
- 32m
Affected: Inyett AutopayDetectInyett AutoInsightInyett OneInyett Automation
Timeline · 2 updates
-
investigating Mar 17, 2026, 07:34 AM UTC
We are currently investigating an issue with failed request from Valu8
-
resolved Mar 17, 2026, 08:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 07:29 AM UTC
- Resolved
- Mar 16, 2026, 08:35 AM UTC
- Duration
- 1h 6m
Affected: Visma.net Payroll NorwayEmployee ManagementVisma.net Calendar AbsenceVisma.net Calendar TimeVisma.net Calendar RosterData ImportHRM Analytics
Timeline · 4 updates
-
investigating Mar 16, 2026, 07:29 AM UTC
We are currently investigating this issue.
-
investigating Mar 16, 2026, 07:33 AM UTC
Follow https://status.visma.com/incidents/4dh2hl1qgphl for upcoming details
-
monitoring Mar 16, 2026, 07:38 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 16, 2026, 08:35 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 07:27 AM UTC
- Resolved
- Mar 16, 2026, 08:45 AM UTC
- Duration
- 1h 17m
Affected: Visma.net ODP
Timeline · 3 updates
-
investigating Mar 16, 2026, 07:27 AM UTC
We are currently investigating an issue in Visma.net Platform with our Identity server component (IDS). Users may experience difficulties with login and accessing some of the applications
-
monitoring Mar 16, 2026, 07:35 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 16, 2026, 08:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 01:33 PM UTC
- Resolved
- Mar 13, 2026, 04:08 PM UTC
- Duration
- 2h 35m
Affected: Plandisc
Timeline · 3 updates
-
investigating Mar 13, 2026, 01:33 PM UTC
We are currently investigating an issue in Plandisc on create.plandisc.com
-
monitoring Mar 13, 2026, 01:37 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 13, 2026, 04:08 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 13, 2026, 12:03 PM UTC
- Resolved
- Mar 13, 2026, 12:36 PM UTC
- Duration
- 32m
Affected: Visma Net API
Timeline · 2 updates
-
investigating Mar 13, 2026, 12:03 PM UTC
We are currently investigating this issue.
-
resolved Mar 13, 2026, 12:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 02:24 PM UTC
- Resolved
- Mar 12, 2026, 04:17 PM UTC
- Duration
- 1h 52m
Affected: Visma NetVisma Net API
Timeline · 6 updates
-
investigating Mar 12, 2026, 02:24 PM UTC
We are currently investigating this issue.
-
identified Mar 12, 2026, 02:41 PM UTC
We have probably found the root cause. Working on a fix now.
-
identified Mar 12, 2026, 03:17 PM UTC
We are continuing to work on a fix for this issue.
-
identified Mar 12, 2026, 03:46 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Mar 12, 2026, 04:17 PM UTC
This incident has been resolved.
-
postmortem Mar 13, 2026, 10:44 AM UTC
The issue was caused by a change in the common authorization service which starting to block access for some of the scopes we are using in the system. As a result login failed for our users which caused the outage. A fix was implemented to support the requested authorization scopes. We are investigating how to prevent this issue in the future.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 05:45 AM UTC
- Resolved
- Mar 12, 2026, 07:57 AM UTC
- Duration
- 2h 12m
Affected: Enterprise Plus
Timeline · 4 updates
-
investigating Mar 12, 2026, 05:45 AM UTC
We are currently investigating this issue.
-
identified Mar 12, 2026, 07:17 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 12, 2026, 07:45 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 12, 2026, 07:57 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 08:05 AM UTC
- Resolved
- Mar 11, 2026, 07:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 11, 2026, 08:05 AM UTC
Maventa experienced degraded performance 2026-03-11 09:24-09:44 returning HTTP 503 errors for small percentage of traffic.
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 12:29 PM UTC
- Resolved
- Mar 04, 2026, 04:28 PM UTC
- Duration
- 3h 59m
Affected: Inyett One
Timeline · 5 updates
-
identified Mar 04, 2026, 12:29 PM UTC
We have identified an issue with indexing related to Detect where transactions from different profiles have been mixed up. We are currently working on a solution to the problem.
-
identified Mar 04, 2026, 12:42 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Mar 04, 2026, 04:14 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Mar 04, 2026, 04:21 PM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 04, 2026, 04:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 09:56 AM UTC
- Resolved
- Mar 03, 2026, 01:37 PM UTC
- Duration
- 3h 41m
Affected: Spiris/Visma Online
Timeline · 3 updates
-
investigating Mar 03, 2026, 09:56 AM UTC
We are currently investigating why customers on Myservices and connected services are experiencing degraded performance
-
monitoring Mar 03, 2026, 11:05 AM UTC
Issues is identified and performance should go back to normal
-
resolved Mar 03, 2026, 01:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 10:13 AM UTC
- Resolved
- Mar 04, 2026, 11:28 AM UTC
- Duration
- 2d 1h
Affected: Visma HoP
Timeline · 3 updates
-
investigating Mar 02, 2026, 10:13 AM UTC
Pašlaik saskaramies ar Visma Paraksts problēmām. Strādājam pie risinājuma. We are having issues with Visma Signature right now. Working on it
-
monitoring Mar 02, 2026, 03:41 PM UTC
A fix has been implemented and we are monitoring the results. Labojums ir ieviests un tiek monitorēti rezultāti.
-
resolved Mar 04, 2026, 11:28 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 08:03 AM UTC
- Resolved
- Mar 02, 2026, 04:34 PM UTC
- Duration
- 8h 30m
Affected: Visma Severa
Timeline · 4 updates
-
investigating Mar 02, 2026, 08:03 AM UTC
We are looking into slowness issues.
-
monitoring Mar 02, 2026, 10:49 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Mar 02, 2026, 10:49 AM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 02, 2026, 04:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 12:02 PM UTC
- Resolved
- Mar 02, 2026, 07:36 AM UTC
- Duration
- 2d 19h
Affected: Visma Net
Timeline · 5 updates
-
investigating Feb 27, 2026, 12:02 PM UTC
We noticed some of our customers experience general slowness using the Visma Net system. Currently we are investigating the problem.
-
identified Feb 27, 2026, 03:15 PM UTC
Based on investigation we did some changes in the system and recycled some of the servers, That resulted in a positive effect on performance.
-
monitoring Feb 27, 2026, 03:17 PM UTC
We see now that performance is coming back to normal for most of our customers. We will keep monitoring the situation.
-
monitoring Feb 27, 2026, 03:17 PM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 02, 2026, 07:36 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 10:51 AM UTC
- Resolved
- Feb 27, 2026, 08:26 AM UTC
- Duration
- 21h 34m
Affected: Enterprise Plus
Timeline · 2 updates
-
investigating Feb 26, 2026, 10:51 AM UTC
We are currently experiencing challenges in invoice processing and billing. These issues are intermittent, and Visma is actively working to gain oversight and identify the root cause of the problem.
-
resolved Feb 27, 2026, 08:26 AM UTC
This Issue has been resolved
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 03:28 PM UTC
- Resolved
- Feb 25, 2026, 03:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 25, 2026, 03:28 PM UTC
Expense is currently unavailable. We are investigating the issue.
Read the full incident report →