Visma incident

Downgraded performance for some customers in Visma Net ERP

Notice Resolved View vendor source →

Visma experienced a notice incident on May 11, 2026 affecting Visma Net, lasting 3h 21m. The incident has been resolved; the full update timeline is below.

Started
May 11, 2026, 11:14 AM UTC
Resolved
May 11, 2026, 02:35 PM UTC
Duration
3h 21m
Detected by Pingoru
May 11, 2026, 11:14 AM UTC

Affected components

Visma Net

Update timeline

  1. identified May 11, 2026, 11:14 AM UTC

    Some customers, belonging to the same server, are experiencing a slower performance. We have identified the problem. There is one customer that are making a lot of calls when trying to connect via API. We are reaching out to the customer.

  2. identified May 11, 2026, 12:42 PM UTC

    We are now upscaling our resources for the server with lower performance.

  3. monitoring May 11, 2026, 01:00 PM UTC

    Performance is normal again, we continue to monitor the situation

  4. resolved May 11, 2026, 02:35 PM UTC

    This incident has been resolved.

  5. postmortem May 20, 2026, 09:24 AM UTC

    Problem was caused by a query that was executed on one of our SQL servers. All customers that were on the same server were impacted by the slowness. We have now improved the functionality related to the query to prevent similar issue from happening in the future.