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.

Source: status.visma.com

188incidents recorded
188last 12 months
92last 90 days
18 hourstypical duration
Incidents per month
02550AprMayJunJulAugSepOct17
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct22%
Pingoru began tracking Visma in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202619280 of 720 (39%)
May 20261862 of 744 (8%)
June 202618301 of 720 (42%)
July 20261430 of 744 (4%)
August 202644137 of 744 (18%)
September 20262019 of 720 (3%)
October 202617130 of 585 (22%)

Incidents, newest first

Major March 16, 2026 Investigating an issue in Visma.net Platform (IDS) 1h 17m Visma.net ODP

Started Mar 16, 2026, 07:27 AM UTC· resolved Mar 16, 2026, 08:45 AM UTC

  1. 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

  2. monitoring Mar 16, 2026, 07:35 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 16, 2026, 08:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 13, 2026 Investigating an issue in Plandisc 2h 35m Plandisc

Started Mar 13, 2026, 01:33 PM UTC· resolved Mar 13, 2026, 04:08 PM UTC

  1. investigating Mar 13, 2026, 01:33 PM UTC

    We are currently investigating an issue in Plandisc on create.plandisc.com

  2. 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.

  3. 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 →

Notice March 13, 2026 Degraded performance on API for Visma net ERP 32m Visma Net API

Started Mar 13, 2026, 12:03 PM UTC· resolved Mar 13, 2026, 12:36 PM UTC

  1. investigating Mar 13, 2026, 12:03 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 13, 2026, 12:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 12, 2026 Visma Net ERP unavailable for some customer - we are looking into it 1h 52m Visma Net, Visma Net API

Started Mar 12, 2026, 02:24 PM UTC· resolved Mar 12, 2026, 04:17 PM UTC

  1. investigating Mar 12, 2026, 02:24 PM UTC

    We are currently investigating this issue.

  2. identified Mar 12, 2026, 02:41 PM UTC

    We have probably found the root cause. Working on a fix now.

  3. identified Mar 12, 2026, 03:17 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Mar 12, 2026, 03:46 PM UTC

    We are continuing to work on a fix for this issue.

  5. resolved Mar 12, 2026, 04:17 PM UTC

    This incident has been resolved.

  6. 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 →

Minor March 12, 2026 Enterprise plus - degraded performance 2h 12m Enterprise Plus

Started Mar 12, 2026, 05:45 AM UTC· resolved Mar 12, 2026, 07:57 AM UTC

  1. investigating Mar 12, 2026, 05:45 AM UTC

    We are currently investigating this issue.

  2. identified Mar 12, 2026, 07:17 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 12, 2026, 07:45 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 12, 2026, 07:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 11, 2026 Maventa experienced degraded performance –

Started Mar 11, 2026, 07:30 AM UTC· resolved Mar 11, 2026, 07:30 AM UTC

  1. 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 →

Critical March 4, 2026 Cross-Profile Transaction Mix-up in Detect Identified 3h 59m Inyett One

Started Mar 04, 2026, 12:29 PM UTC· resolved Mar 04, 2026, 04:28 PM UTC

  1. 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.

  2. identified Mar 04, 2026, 12:42 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Mar 04, 2026, 04:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Mar 04, 2026, 04:21 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 04, 2026, 04:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 3, 2026 My Services/ Spiris degrading perfomance 3h 41m Spiris/Visma Online

Started Mar 03, 2026, 09:56 AM UTC· resolved Mar 03, 2026, 01:37 PM UTC

  1. investigating Mar 03, 2026, 09:56 AM UTC

    We are currently investigating why customers on Myservices and connected services are experiencing degraded performance

  2. monitoring Mar 03, 2026, 11:05 AM UTC

    Issues is identified and performance should go back to normal

  3. resolved Mar 03, 2026, 01:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 2, 2026 Visma HoP issue with electronic document signing 2d 1h Visma HoP

Started Mar 02, 2026, 10:13 AM UTC· resolved Mar 04, 2026, 11:28 AM UTC

  1. 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

  2. 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.

  3. resolved Mar 04, 2026, 11:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026 Slowness in Visma Severa 8h 30m Visma Severa

Started Mar 02, 2026, 08:03 AM UTC· resolved Mar 02, 2026, 04:34 PM UTC

  1. investigating Mar 02, 2026, 08:03 AM UTC

    We are looking into slowness issues.

  2. monitoring Mar 02, 2026, 10:49 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Mar 02, 2026, 10:49 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Mar 02, 2026, 04:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 27, 2026 Visma Net - General slowness 2d 19h Visma Net

Started Feb 27, 2026, 12:02 PM UTC· resolved Mar 02, 2026, 07:36 AM UTC

  1. 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.

  2. 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.

  3. 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.

  4. monitoring Feb 27, 2026, 03:17 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 02, 2026, 07:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 26, 2026 Challenges in invoice processing and billing 21h 34m Enterprise Plus

Started Feb 26, 2026, 10:51 AM UTC· resolved Feb 27, 2026, 08:26 AM UTC

  1. 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.

  2. resolved Feb 27, 2026, 08:26 AM UTC

    This Issue has been resolved

Read the full incident report →

Notice February 25, 2026 Investigating an issue in Visma.net Expense –

Started Feb 25, 2026, 03:00 PM UTC· resolved Feb 25, 2026, 03:00 PM UTC

  1. resolved Feb 25, 2026, 03:28 PM UTC

    Expense is currently unavailable. We are investigating the issue.

Read the full incident report →

Minor February 24, 2026 Maventa is experiencing degraded performance 1d 21h Maventa / Visma .net AutoInvoice

Started Feb 24, 2026, 10:47 AM UTC· resolved Feb 26, 2026, 08:05 AM UTC

  1. investigating Feb 24, 2026, 10:47 AM UTC

    We are currently investigating this issue. But we are seeing increased failure rates and timeouts in the logs.

  2. investigating Feb 24, 2026, 11:17 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 24, 2026, 01:59 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. investigating Feb 25, 2026, 07:24 AM UTC

    Previous fix did not fix the root cause. We are still investigating

  5. identified Feb 25, 2026, 03:10 PM UTC

    The issue has been identified and a fix is being implemented.

  6. monitoring Feb 25, 2026, 03:42 PM UTC

    A fix has been implemented and we are monitoring the results.

  7. resolved Feb 26, 2026, 08:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 20, 2026 GAiA Assistant API unresponsive 20m

Started Feb 20, 2026, 02:00 PM UTC· resolved Feb 20, 2026, 02:20 PM UTC

  1. resolved Feb 20, 2026, 02:27 PM UTC

    API unresponsive for about 25 minutes after a database migration edit was lost in a canceled deployment.

Read the full incident report →

Notice February 9, 2026 Invoicing issues in Business NXT –

Started Feb 09, 2026, 07:00 AM UTC· resolved Feb 09, 2026, 07:00 AM UTC

  1. resolved Feb 09, 2026, 12:41 PM UTC

    Today we had an issue with invoicing in Business NXT. The issue started at 08:15 and was corrected 11:40. About the issue: Invoice printouts were missing important information. This happened when using Finalize on an invoice for later printout or when using Send and having Autoinvoice as Document delivery method. The only way to properly correct this is to credit the invoices and send them again.

Read the full incident report →

Minor February 6, 2026 Enterprise plus web unstable 29m Enterprise Plus

Started Feb 06, 2026, 12:51 PM UTC· resolved Feb 06, 2026, 01:21 PM UTC

  1. investigating Feb 06, 2026, 12:51 PM UTC

    We are currently investigation an issue, some web-modules are unstable.

  2. resolved Feb 06, 2026, 01:21 PM UTC

    The incident has been resolved and the system is stable.

Read the full incident report →