Visma Outage History

Visma is up right now

Visma had 125 outages in the last 2 years totaling 82h 6m of downtime — averaging 5.1 incidents per month.

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

Source: https://status.visma.com

Minor September 17, 2026

Degraded performance for Flyt Barnehage api

Detected by Pingoru
Sep 17, 2026, 08:42 AM UTC
Resolved
Sep 17, 2026, 12:19 PM UTC
Duration
3h 36m
Affected: Flyt BarnehageMin Barnehage
Timeline · 4 updates
  1. investigating Sep 17, 2026, 08:42 AM UTC

    We are currently investigating this issue.

  2. investigating Sep 17, 2026, 10:48 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 17, 2026, 10:48 AM UTC

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

  4. resolved Sep 17, 2026, 12:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 14, 2026

[Auto] Inqom Api availability degraded

Detected by Pingoru
Sep 14, 2026, 09:44 AM UTC
Resolved
Sep 14, 2026, 09:54 AM UTC
Duration
9m
Affected: Inqom Api
Timeline · 2 updates
  1. investigating Sep 14, 2026, 09:44 AM UTC

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

  2. resolved Sep 14, 2026, 09:54 AM UTC

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

Read the full incident report →

Major September 14, 2026

[Auto] Accounting availability degraded

Detected by Pingoru
Sep 14, 2026, 09:35 AM UTC
Resolved
Sep 14, 2026, 09:52 AM UTC
Duration
17m
Affected: Accounting
Timeline · 2 updates
  1. investigating Sep 14, 2026, 09:35 AM UTC

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

  2. resolved Sep 14, 2026, 09:52 AM UTC

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

Read the full incident report →

Major September 11, 2026

[Auto] Fscp availability degraded

Detected by Pingoru
Sep 11, 2026, 09:18 AM UTC
Resolved
Sep 11, 2026, 09:29 AM UTC
Duration
11m
Affected: Fscp
Timeline · 2 updates
  1. investigating Sep 11, 2026, 09:18 AM UTC

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

  2. resolved Sep 11, 2026, 09:29 AM UTC

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

Read the full incident report →

Minor September 11, 2026

Dashboard component causing errors or not opening

Detected by Pingoru
Sep 11, 2026, 05:26 AM UTC
Resolved
Sep 11, 2026, 08:59 AM UTC
Duration
3h 32m
Affected: Visma Severa
Timeline · 5 updates
  1. investigating Sep 11, 2026, 05:26 AM UTC

    We are looking into this issue

  2. identified Sep 11, 2026, 06:06 AM UTC

    We have identified the issue and we are implementing a fix

  3. monitoring Sep 11, 2026, 08:41 AM UTC

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

  4. monitoring Sep 11, 2026, 08:42 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Sep 11, 2026, 08:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 3, 2026

Winvoice Down

Detected by Pingoru
Sep 03, 2026, 07:48 AM UTC
Resolved
Sep 03, 2026, 07:48 AM UTC
Duration
Affected: Winvoice
Timeline · 2 updates
  1. resolved Sep 03, 2026, 07:48 AM UTC

    Winvoice down due to a certificate management problem in Azure

  2. postmortem Sep 03, 2026, 07:49 AM UTC

    **Issue Overview** Winvoice experienced temporary downtime due to a DNS verification update required for Azure certificate management. **Details & Resolution** Azure required updated DNS records to be set at our domain registrar to complete automated SSL certificate validation. Once our team configured the required records and DNS propagation completed, Azure successfully validated the domain and service access was fully restored. **Next Steps** To prevent similar occurrences, we are migrating our DNS hosting to **Azure DNS Zone** and implementing **Azure Front Door**. This should fully automate our SSL certificate lifecycle management and streamline DNS record management directly within Azure.

Read the full incident report →

Major September 1, 2026

[Auto] Accounting documents availability degraded

Detected by Pingoru
Sep 01, 2026, 08:21 PM UTC
Resolved
Sep 01, 2026, 08:28 PM UTC
Duration
7m
Affected: Accounting documents
Timeline · 2 updates
  1. investigating Sep 01, 2026, 08:21 PM UTC

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

  2. resolved Sep 01, 2026, 08:28 PM UTC

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

Read the full incident report →

Minor August 31, 2026

Driftsavvik: Ustabilitet på Amazon WorkSpaces Applications

Detected by Pingoru
Aug 31, 2026, 06:26 AM UTC
Resolved
Aug 31, 2026, 12:44 PM UTC
Duration
6h 18m
Affected: Enterprise Plus
Timeline · 6 updates
  1. investigating Aug 31, 2026, 06:26 AM UTC

    Driftsavvik: Ustabilitet på Amazon WorkSpaces Applications Vi opplever for øyeblikket teknisk ustabilitet på Amazon WorkSpaces Applications. Status: Teknisk team jobber for fullt med å feilsøke og utbedre problemet. Konsekvens: Brukere kan oppleve treghet, feilmeldinger eller utfordringer med å koble til sesjoner. Vi beklager ulempene dette medfører, og kommer med en ny oppdatering så snart vi har mer informasjon. Service Alert: Amazon WorkSpaces Applications Instability We are currently experiencing technical instability with Amazon WorkSpaces Applications. Status: Our technical team is actively investigating and working to resolve the issue. Impact: Users may experience slowness, error messages, or trouble connecting to sessions. We apologize for any inconvenience and will share an update as soon as more information is available.

  2. investigating Aug 31, 2026, 06:27 AM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 31, 2026, 06:28 AM UTC

    We are continuing to investigate this issue.

  4. identified Aug 31, 2026, 10:00 AM UTC

    Problemene har blitt identifisert, og vi jobber med å løse de.

  5. monitoring Aug 31, 2026, 11:30 AM UTC

    Vi har funnet problemet, og monitorerer saken.

  6. resolved Aug 31, 2026, 12:44 PM UTC

    Vi har nå lagt ut en rettelse som skal løse problemet der basismodul-ikonene på startsiden ikke ga noe svar, eller ga en feilmelding, når de ble åpnet.

Read the full incident report →

Major August 30, 2026

[Auto] Stability availability degraded

Detected by Pingoru
Aug 30, 2026, 02:23 AM UTC
Resolved
Aug 30, 2026, 02:31 AM UTC
Duration
8m
Affected: Stability
Timeline · 2 updates
  1. investigating Aug 30, 2026, 02:23 AM UTC

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

  2. resolved Aug 30, 2026, 02:31 AM UTC

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

Read the full incident report →

Major August 30, 2026

[Auto] Marketplace availability degraded

Detected by Pingoru
Aug 30, 2026, 02:22 AM UTC
Resolved
Aug 30, 2026, 02:32 AM UTC
Duration
9m
Affected: Marketplace
Timeline · 2 updates
  1. investigating Aug 30, 2026, 02:22 AM UTC

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

  2. resolved Aug 30, 2026, 02:32 AM UTC

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

Read the full incident report →

Major August 30, 2026

[Auto] Integretionmicrosoft365 availability degraded

Detected by Pingoru
Aug 30, 2026, 02:22 AM UTC
Resolved
Aug 30, 2026, 02:32 AM UTC
Duration
10m
Affected: Integretionmicrosoft365
Timeline · 2 updates
  1. investigating Aug 30, 2026, 02:22 AM UTC

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

  2. resolved Aug 30, 2026, 02:32 AM UTC

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

Read the full incident report →

Major August 30, 2026

[Auto] Interco availability degraded

Detected by Pingoru
Aug 30, 2026, 02:22 AM UTC
Resolved
Aug 30, 2026, 02:33 AM UTC
Duration
11m
Affected: Interco
Timeline · 2 updates
  1. investigating Aug 30, 2026, 02:22 AM UTC

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

  2. resolved Aug 30, 2026, 02:33 AM UTC

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

Read the full incident report →

Major August 30, 2026

[Auto] Billing availability degraded

Detected by Pingoru
Aug 30, 2026, 02:22 AM UTC
Resolved
Aug 30, 2026, 05:38 AM UTC
Duration
3h 16m
Affected: Billing
Timeline · 2 updates
  1. investigating Aug 30, 2026, 02:22 AM UTC

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

  2. resolved Aug 30, 2026, 05:38 AM UTC

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

Read the full incident report →

Major August 30, 2026

[Auto] Archive availability degraded

Detected by Pingoru
Aug 30, 2026, 02:21 AM UTC
Resolved
Aug 30, 2026, 02:33 AM UTC
Duration
11m
Affected: Archive
Timeline · 2 updates
  1. investigating Aug 30, 2026, 02:21 AM UTC

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

  2. resolved Aug 30, 2026, 02:33 AM UTC

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

Read the full incident report →

Major August 30, 2026

[Auto] Revision availability degraded

Detected by Pingoru
Aug 30, 2026, 02:21 AM UTC
Resolved
Aug 30, 2026, 05:37 AM UTC
Duration
3h 16m
Affected: Revision
Timeline · 2 updates
  1. investigating Aug 30, 2026, 02:21 AM UTC

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

  2. resolved Aug 30, 2026, 05:37 AM UTC

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

Read the full incident report →

Minor August 27, 2026

Degraded performance for Enterprise plus

Detected by Pingoru
Aug 27, 2026, 02:53 PM UTC
Resolved
Aug 27, 2026, 02:58 PM UTC
Duration
5m
Affected: Enterprise Plus
Timeline · 2 updates
  1. investigating Aug 27, 2026, 02:53 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 27, 2026, 02:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 26, 2026

Smartscan - major outage

Detected by Pingoru
Aug 26, 2026, 10:03 AM UTC
Resolved
Aug 26, 2026, 12:35 PM UTC
Duration
2h 31m
Affected: Machine Learning Assets
Timeline · 5 updates
  1. investigating Aug 26, 2026, 10:03 AM UTC

    We are currently investigating this issue.

  2. identified Aug 26, 2026, 10:07 AM UTC

    The issue is identified - not enough GPU resources.

  3. identified Aug 26, 2026, 10:31 AM UTC

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

  4. monitoring Aug 26, 2026, 11:50 AM UTC

    Smartscan is stabilising, we continue to monitor the situation

  5. resolved Aug 26, 2026, 12:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 26, 2026

Visma Hop Authentication and DLP degraded performance

Detected by Pingoru
Aug 26, 2026, 08:53 AM UTC
Resolved
Aug 26, 2026, 11:55 AM UTC
Duration
3h 2m
Affected: Visma HoP
Timeline · 3 updates
  1. investigating Aug 26, 2026, 08:53 AM UTC

    We are currently experiencing degraded performance affecting HoP authentication and DLP functionality. Our team is actively investigating the issue and working to restore full service as quickly as possible. We will provide updates as more information becomes available.

  2. monitoring Aug 26, 2026, 10:24 AM UTC

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

  3. resolved Aug 26, 2026, 11:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 26, 2026

Driftsmelding: Vedvarende utfordringer med Id-Porten

Detected by Pingoru
Aug 26, 2026, 06:38 AM UTC
Resolved
Aug 27, 2026, 11:24 AM UTC
Duration
1d 4h
Affected: Visma Enterprise BIEnterprise PlusAccounting ServicesEnterprise Ressursstyring Plus
Timeline · 5 updates
  1. investigating Aug 26, 2026, 06:38 AM UTC

    Vi gjør oppmerksom på at Id-Porten fremdeles har tekniske utfordringer, noe som kan medføre innloggingsproblemer i Enterprise Plus. Status: Teknisk team jobber fortløpende med å løse saken. Konsekvens: Innlogging på Enterprise Plus kan mislykkes eller ta lengre tid enn normalt. Vi beklager ulempene dette medfører, og oppdaterer så snart situasjonen er løst. Takk for tålmodigheten! Please be advised that Id-Porten is still experiencing technical difficulties, which may cause login issues for Enterprise Plus. Status: The technical team is actively working to resolve the issue. Impact: Logging in to Enterprise Plus may fail or take longer than usual. We apologize for any inconvenience this may cause and will provide an update as soon as the situation is resolved. Thank you for your patience!

  2. investigating Aug 26, 2026, 06:44 AM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 26, 2026, 06:47 AM UTC

    We are continuing to investigate this issue.

  4. investigating Aug 27, 2026, 11:22 AM UTC

    Status 09:00 Det tyder på at angrepet er avsluttet. Våre løsninger har fungert i stor grad som normalt gjennom natten, og trafikken tar seg opp på vanlig måte utover dagen. Det er kun noe trafikk fra utlandet som fortsatt har hatt driftsforstyrrelser som følge av angrepet. Vi har beholdt beredskapstiltakene gjennom natten som en forsikring, og følger situasjonen videre utover dagen. Angrepet startet natt til mandag kl. 03.38 og stoppet ved 19.30-tiden onsdag kveld. Med unntak av korte perioder har ID-porten og fellesløsningene vært tilgjengelige hele tiden. Vi forventer å komme over til normal drift i løpet av de nærmeste dagene.

  5. resolved Aug 27, 2026, 11:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 24, 2026

Maventa: Problems with Peppol sends and lookups in Norway

Detected by Pingoru
Aug 24, 2026, 06:13 AM UTC
Resolved
Aug 24, 2026, 10:05 AM UTC
Duration
3h 52m
Affected: Maventa / Visma .net AutoInvoice
Timeline · 3 updates
  1. identified Aug 24, 2026, 06:13 AM UTC

    The Norwegian Peppol SMP Elma is having an incident: https://status.digdir.no/incidents/d7tgwqgzd742 This causes delays in invoice deliveries in Maventa and failures (lookup_retry_error) in lookups.

  2. monitoring Aug 24, 2026, 07:20 AM UTC

    Issues seem to be resolved at Elma SMP - no delays currently

  3. resolved Aug 24, 2026, 10:05 AM UTC

    Issues with the Norwegian Peppol SMP Elma resolved at Digdir side.

Read the full incident report →

Major August 19, 2026

Issue in Business NXT

Detected by Pingoru
Aug 19, 2026, 09:02 AM UTC
Resolved
Aug 19, 2026, 12:08 PM UTC
Duration
3h 6m
Affected: Business NXT ERP
Timeline · 2 updates
  1. monitoring Aug 19, 2026, 09:02 AM UTC

    We have an issue with synchronization between services (Approval and Admin) and Business NXT. The issues should be fixed, but there is some delay while synchronization processes the queue that has built up. We will keep monitoring and ensure everything works as expected.

  2. resolved Aug 19, 2026, 12:08 PM UTC

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

Read the full incident report →

Major August 16, 2026

[Auto] Silae availability degraded

Detected by Pingoru
Aug 16, 2026, 02:14 AM UTC
Resolved
Aug 16, 2026, 02:22 AM UTC
Duration
7m
Affected: Silae
Timeline · 2 updates
  1. investigating Aug 16, 2026, 02:14 AM UTC

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

  2. resolved Aug 16, 2026, 02:22 AM UTC

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

Read the full incident report →