Visma Outage History

Visma is up right now

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

Source: https://status.visma.com

Minor February 24, 2026

Maventa is experiencing degraded performance

Detected by Pingoru
Feb 24, 2026, 10:47 AM UTC
Resolved
Feb 26, 2026, 08:05 AM UTC
Duration
1d 21h
Affected: Maventa / Visma .net AutoInvoice
Timeline · 7 updates
  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

Detected by Pingoru
Feb 20, 2026, 02:00 PM UTC
Resolved
Feb 20, 2026, 02:20 PM UTC
Duration
20m
Timeline · 1 update
  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

Detected by Pingoru
Feb 09, 2026, 12:41 PM UTC
Resolved
Feb 09, 2026, 07:00 AM UTC
Duration
—
Timeline · 1 update
  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 →

Critical February 9, 2026

Investigating an issue in Hubix

Detected by Pingoru
Feb 09, 2026, 08:21 AM UTC
Resolved
Feb 09, 2026, 08:49 AM UTC
Duration
28m
Affected: InExchangeHubix
Timeline · 3 updates
  1. investigating Feb 09, 2026, 08:21 AM UTC

    We have identified the cause of the incident and are currently working on finding a solution for this. All interoperability endpoints are down, which includes lookup, peppol and email registrations and print webhook.

  2. monitoring Feb 09, 2026, 08:31 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 Feb 09, 2026, 08:49 AM UTC

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

Read the full incident report →

Minor February 6, 2026

Enterprise plus web unstable

Detected by Pingoru
Feb 06, 2026, 12:51 PM UTC
Resolved
Feb 06, 2026, 01:21 PM UTC
Duration
29m
Affected: Enterprise Plus
Timeline · 2 updates
  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 →

Looking to track Visma downtime and outages?

Pingoru polls Visma's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Visma reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Visma alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Visma for free

5 free monitors · No credit card required