Visma Outage History

Visma degraded · 1 active incident View live status →

Visma had 98 outages in the last 2 years totaling 405h 19m of downtime — averaging 4 incidents per month.

There were 98 Visma outages since February 6, 2026 totaling 405h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.visma.com

Notice August 3, 2026

Flyt Inschool - ID-porten is unavailable

Detected by Pingoru
Aug 03, 2026, 08:58 AM UTC
Resolved
Aug 03, 2026, 01:18 PM UTC
Duration
4h 19m
Affected: InSchool Management Information System (MIS)
Timeline · 3 updates
  1. investigating Aug 03, 2026, 08:58 AM UTC

    ID-porten is unavailable due to DigDir technical issues https://status.digdir.no/incidents/d7hvqmf2yr3l

  2. investigating Aug 03, 2026, 10:55 AM UTC

    In addition to ID-porten, the following services are also unavailable due to DigDir issues: 1. SvarUt shipments 2. Freg and Contact services https://status.digdir.no/incidents/d7hvqmf2yr3l

  3. resolved Aug 03, 2026, 01:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 31, 2026

[Auto] Meg availability degraded

Detected by Pingoru
Jul 31, 2026, 02:11 AM UTC
Resolved
Jul 31, 2026, 02:18 AM UTC
Duration
6m
Affected: Meg
Timeline · 2 updates
  1. investigating Jul 31, 2026, 02:11 AM UTC

    Meg is currently experiencing a major outage. Our team is investigating the issue.

  2. resolved Jul 31, 2026, 02:18 AM UTC

    The incident affecting Meg has been resolved. We will keep monitoring to ensure everything remains stable.

Read the full incident report →

Major July 31, 2026

[Auto] Silae availability degraded

Detected by Pingoru
Jul 31, 2026, 02:11 AM UTC
Resolved
Jul 31, 2026, 02:24 AM UTC
Duration
13m
Affected: Silae
Timeline · 2 updates
  1. investigating Jul 31, 2026, 02:11 AM UTC

    Silae is currently experiencing a major outage. Our team is investigating the issue.

  2. resolved Jul 31, 2026, 02:24 AM UTC

    The incident affecting Silae has been resolved. We will keep monitoring to ensure everything remains stable.

Read the full incident report →

Major July 31, 2026

[Auto] Factofrance availability degraded

Detected by Pingoru
Jul 31, 2026, 02:09 AM UTC
Resolved
Jul 31, 2026, 02:20 AM UTC
Duration
11m
Affected: Factofrance
Timeline · 2 updates
  1. investigating Jul 31, 2026, 02:09 AM UTC

    Factofrance is currently experiencing a major outage. Our team is investigating the issue.

  2. resolved Jul 31, 2026, 02:20 AM UTC

    The incident affecting Factofrance has been resolved. We will keep monitoring to ensure everything remains stable.

Read the full incident report →

Major July 30, 2026

Investigating an issue in Business NXT

Detected by Pingoru
Jul 30, 2026, 11:52 AM UTC
Resolved
Jul 31, 2026, 06:35 AM UTC
Duration
18h 42m
Affected: Business NXT ERPBusiness NXT ERP API
Timeline · 4 updates
  1. investigating Jul 30, 2026, 11:52 AM UTC

    We are currently investigating an issue in Business NXT, where database operations fail. The errors are mainly related to the Order Line and Product Transaction tables, but might also affect other tables. We will be back with more information shortly.

  2. investigating Jul 30, 2026, 12:04 PM UTC

    We have identified the cause of the incident and are currently working on finding a solution. We will be back with an estimated time of the fix soon.

  3. monitoring Jul 30, 2026, 04:08 PM UTC

    This issue should be solved for all customers. We will keep monitoring to ensure high quality.

  4. resolved Jul 31, 2026, 06:35 AM UTC

    The issue is now resolved and the service is up and running as normal.

Read the full incident report →

Critical July 30, 2026

Numo outage

Detected by Pingoru
Jul 30, 2026, 11:20 AM UTC
Resolved
Jul 30, 2026, 12:34 PM UTC
Duration
1h 14m
Affected: Numo
Timeline · 5 updates
  1. investigating Jul 30, 2026, 11:20 AM UTC

    We are currently investigating this issue.

  2. identified Jul 30, 2026, 12:05 PM UTC

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

  3. monitoring Jul 30, 2026, 12:07 PM UTC

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

  4. monitoring Jul 30, 2026, 12:13 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jul 30, 2026, 12:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 29, 2026

Visma.net ERP Payment Service

Detected by Pingoru
Jul 29, 2026, 05:06 AM UTC
Resolved
Jul 29, 2026, 05:31 AM UTC
Duration
25m
Affected: Visma.net ERP Payment Service
Timeline · 3 updates
  1. investigating Jul 29, 2026, 05:06 AM UTC

    We are currently investigating a service disruption in Visma.net ERP Payment Service. We will provide more information shortly.

  2. monitoring Jul 29, 2026, 05:19 AM 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 Jul 29, 2026, 05:31 AM UTC

    The issue is now resolved and the service is up and running as normal.

Read the full incident report →

Minor July 16, 2026

EnterprisePlus - Degraded Performance

Detected by Pingoru
Jul 16, 2026, 09:07 PM UTC
Resolved
Jul 17, 2026, 04:17 AM UTC
Duration
7h 10m
Affected: Enterprise Plus
Timeline · 2 updates
  1. investigating Jul 16, 2026, 09:07 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 17, 2026, 04:17 AM UTC

    The issue is now resolved and the service is up and running as normal.

Read the full incident report →

Major July 2, 2026

We are currently investigating a service disruption in Spiris - Bokföring & Fakturering/Visma eAccounting.

Detected by Pingoru
Jul 02, 2026, 09:46 AM UTC
Resolved
Jul 02, 2026, 10:21 AM UTC
Duration
34m
Affected: Spiris - Bokföring & Fakturering/Visma eAccountingSpiris - LönSpiris - Bokföring & Fakturering Externt API/Visma eAccounting External API
Timeline · 3 updates
  1. investigating Jul 02, 2026, 09:46 AM UTC

    We are currently investigating a service disruption, some customers may expierince slow performance.

  2. monitoring Jul 02, 2026, 10:14 AM UTC

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

  3. resolved Jul 02, 2026, 10:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 1, 2026

Investigating an issue in Approval login

Detected by Pingoru
Jul 01, 2026, 01:57 PM UTC
Resolved
Jul 01, 2026, 02:22 PM UTC
Duration
24m
Timeline · 4 updates
  1. investigating Jul 01, 2026, 01:57 PM UTC

    We are currently investigating an issue regarding login to Approval.

  2. identified Jul 01, 2026, 02:10 PM UTC

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

  3. monitoring Jul 01, 2026, 02:13 PM UTC

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

  4. resolved Jul 01, 2026, 02:22 PM UTC

    This incident has been resolved. The service is up and running again.

Read the full incident report →

Notice June 23, 2026

Stability issues in the Business NXT API

Detected by Pingoru
Jun 23, 2026, 07:36 AM UTC
Resolved
Jun 23, 2026, 07:32 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 23, 2026, 07:36 AM UTC

    We experienced stability issues with the Business NXT API this morning. The incident began at 04:56 CET and was fully resolved by 08:35 CET. We apologize for any inconvenience this caused our customers and integration partners.

Read the full incident report →

Minor June 18, 2026

Business NXT: some webhook messages were lost

Detected by Pingoru
Jun 18, 2026, 11:38 AM UTC
Resolved
Jun 16, 2026, 09:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 18, 2026, 11:38 AM UTC

    In the period between 11:45 CET and 12:20 CET the distribution of webhook messages in Business NXT had issues and some webhooks were lost.

Read the full incident report →

Notice June 15, 2026

Portal (Inyett One) temporarily down and not accessible

Detected by Pingoru
Jun 15, 2026, 12:52 PM UTC
Resolved
Jun 15, 2026, 12:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 15, 2026, 12:52 PM UTC

    Due to a change in configuration and a cached instance our portal (Inyett One) lost communication with one of our backend resources. This was remediated by recreating the instances for the app service that was holding the cached value.

Read the full incident report →

Minor June 11, 2026

Glup: Kurskatalog feil

Detected by Pingoru
Jun 11, 2026, 12:07 PM UTC
Resolved
Jun 12, 2026, 06:49 AM UTC
Duration
18h 42m
Affected: Glup
Timeline · 2 updates
  1. identified Jun 11, 2026, 12:07 PM UTC

    sortering i kurskatalog er feil. Mulig å gjennomføre kurs og søke etter kurs i katalogen. Feilen er lokalisert og under retting.

  2. resolved Jun 12, 2026, 06:49 AM UTC

    Feilen er rettet.

Read the full incident report →

Minor June 11, 2026

Not possible to send e-invoices in Spiris Accounting, Invoicing & Payroll / Visma eAccounting and Visma Admininstration

Detected by Pingoru
Jun 11, 2026, 07:30 AM UTC
Resolved
Jun 11, 2026, 09:20 AM UTC
Duration
1h 50m
Affected: Spiris - Bokföring & Fakturering/Visma eAccountingSpiris - e-fakturering Bokföring & Fakturering/Administration
Timeline · 5 updates
  1. investigating Jun 11, 2026, 07:30 AM UTC

    We are currently investigating an issue in Spiris Accounting, Invoicing & Payroll, Visma eAccounting, and Visma Administration. At the moment, it is not possible to send e-invoices. We are investigating the issue.

  2. identified Jun 11, 2026, 07:57 AM UTC

    We are still investigating the issue preventing e-invoices from being sent. It is still possible We will update you again as soon as we have any new information.

  3. identified Jun 11, 2026, 08:33 AM UTC

    We are working to resolve the issue as quickly as possible. We will update you again as soon as we have new information.

  4. monitoring Jun 11, 2026, 08:41 AM UTC

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

  5. resolved Jun 11, 2026, 09:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026

Problems with periodic allocations for Control Edge

Detected by Pingoru
Jun 10, 2026, 11:52 AM UTC
Resolved
Jun 10, 2026, 08:33 PM UTC
Duration
8h 41m
Affected: Control Edge
Timeline · 4 updates
  1. investigating Jun 10, 2026, 11:52 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 10, 2026, 11:52 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 10, 2026, 05:39 PM UTC

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

  4. resolved Jun 10, 2026, 08:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026

User sessions partly unavailable

Detected by Pingoru
Jun 10, 2026, 07:11 AM UTC
Resolved
Jun 10, 2026, 08:05 AM UTC
Duration
54m
Affected: Visma.net ODPVisma.net Payroll Norway
Timeline · 6 updates
  1. investigating Jun 10, 2026, 07:11 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 10, 2026, 07:15 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 10, 2026, 07:16 AM UTC

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

  4. monitoring Jun 10, 2026, 07:32 AM UTC

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

  5. monitoring Jun 10, 2026, 07:37 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jun 10, 2026, 08:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 9, 2026

Investigating an issue in Visma Recruit

Detected by Pingoru
Jun 09, 2026, 12:35 PM UTC
Resolved
Jun 09, 2026, 08:27 PM UTC
Duration
7h 51m
Affected: Visma Recruit
Timeline · 4 updates
  1. investigating Jun 09, 2026, 12:35 PM UTC

    We are currently investigating an issue in Visma Recruit.

  2. investigating Jun 09, 2026, 04:20 PM UTC

    In Swedish; Vi har identifierat orsaken till incidenten, som är kopplad till dagens release. Vi arbetar för närvarande med att ta fram en lösning och återkommer med en ny statusuppdatering så snart vi har mer information. Vi beklagar besväret. In English; We have identified the cause of the incident, which is related to today's release. We are currently working on a solution and will provide a status update as soon as we have more information. We apologize for the inconvenience

  3. monitoring Jun 09, 2026, 05:11 PM UTC

    På svenska: Tjänsten är åter i full drift och problemet ska nu vara löst för samtliga kunder. Vi övervakar systemet noggrant under den närmaste tiden för att säkerställa stabil drift och hög kvalitet. In English: The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.

  4. resolved Jun 09, 2026, 08:27 PM UTC

    Driftstörningen är nu helt löst och Visma Recruit är i normal drift sedan klockan 19:00. Vi tackar för ert tålamod under tiden vi arbetade med att åtgärda felet! In English: The issue is now fully resolved and Visma Recruit has been running as normal since 19:00. Thank you for your patience while we worked to resolve this issue!

Read the full incident report →

Major June 9, 2026

Spiris - Deklaration & Årsredovisning/Årsbokslut, Skatt & Bokslut and Koncernredovisning - Issues with downloading documents and degraded performance

Detected by Pingoru
Jun 09, 2026, 07:59 AM UTC
Resolved
Jun 09, 2026, 08:21 AM UTC
Duration
22m
Affected: Spiris - Skatt & BokslutSpiris - KoncernredovisningSpiris - Deklaration & Årsredovisning/Årsbokslut
Timeline · 2 updates
  1. investigating Jun 09, 2026, 07:59 AM UTC

    We are investigating issues with document downloads and degraded performance.

  2. resolved Jun 09, 2026, 08:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 9, 2026

Performance degradation in Payroll

Detected by Pingoru
Jun 09, 2026, 07:40 AM UTC
Resolved
Jun 09, 2026, 01:54 PM UTC
Duration
6h 14m
Affected: Visma.net Payroll Norway
Timeline · 3 updates
  1. investigating Jun 09, 2026, 07:40 AM UTC

    We are currently looking into performance degradation in Payroll.

  2. monitoring Jun 09, 2026, 12:22 PM UTC

    We've deployed fixes to address the degraded performance and the service is now operating normally. We'll continue to monitor to confirm full resolution.

  3. resolved Jun 09, 2026, 01:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 8, 2026

Slowness in Payroll Norway

Detected by Pingoru
Jun 08, 2026, 12:46 PM UTC
Resolved
Jun 09, 2026, 05:09 AM UTC
Duration
16h 23m
Affected: Visma.net Payroll Norway
Timeline · 3 updates
  1. investigating Jun 08, 2026, 12:46 PM UTC

    We are experiencing unusual slowness, we are investigating.

  2. investigating Jun 08, 2026, 01:58 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 09, 2026, 05:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 8, 2026

Degraded performance Flyt Route Planner

Detected by Pingoru
Jun 08, 2026, 09:08 AM UTC
Resolved
Jun 08, 2026, 09:41 AM UTC
Duration
33m
Affected: Visma Flyt Route Planner
Timeline · 2 updates
  1. identified Jun 08, 2026, 09:08 AM UTC

    The issue has been identified.

  2. resolved Jun 08, 2026, 09:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 6, 2026

Investigating an issue in Business NXT API

Detected by Pingoru
Jun 06, 2026, 07:22 PM UTC
Resolved
Jun 07, 2026, 02:18 PM UTC
Duration
18h 56m
Affected: Business NXT ERP API
Timeline · 3 updates
  1. investigating Jun 06, 2026, 07:22 PM UTC

    We are currently investigating an issue in Business NXT API. Some mutations do not return a result even if they are executed successfully. Reading operations are working as expected. We will be back with more information shortly.

  2. monitoring Jun 06, 2026, 08:20 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 Jun 07, 2026, 02:18 PM UTC

    The issue is now resolved and the service is up and running as normal.

Read the full incident report →

Minor June 5, 2026

Flyt Common High Response time

Detected by Pingoru
Jun 05, 2026, 11:16 AM UTC
Resolved
Jun 17, 2026, 09:00 AM UTC
Duration
11d 21h
Affected: Visma Flyt PPTVisma Flyt BVVVisma Flyt HelseVisma Flyt Sikker SakFlyt Barnevern
Timeline · 6 updates
  1. investigating Jun 05, 2026, 11:16 AM UTC

    We're experiencing again slowness in all our Applications We're looking into the issue as we speak

  2. identified Jun 05, 2026, 11:44 AM UTC

    High response time seems to be due to high load on a network shared resource we're using with other projects. Network team will undergo an emergency maintenance window to increase resources on that infrastructure in order to handle more load during red periods. Emergency Maintenance will happen soon, when everything will be settled time will as well be announced

  3. monitoring Jun 05, 2026, 12:43 PM UTC

    Emergency change has been implemented, server resources seem to handle better the load, we're now monitoring the results and if all our infrastructure goes back to normal behaviour

  4. monitoring Jun 08, 2026, 12:46 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Jun 10, 2026, 07:47 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Jun 17, 2026, 09:00 AM UTC

    This incident has been resolved.

Read the full incident report →