Visma incident

Problems with login in Visma net

Critical Resolved View vendor source →

Visma experienced a critical incident on May 16, 2026 affecting Visma Net and Visma Net API, lasting 49m. The incident has been resolved; the full update timeline is below.

Started
May 16, 2026, 05:24 AM UTC
Resolved
May 16, 2026, 06:14 AM UTC
Duration
49m
Detected by Pingoru
May 16, 2026, 05:24 AM UTC

Affected components

Visma NetVisma Net API

Update timeline

  1. investigating May 16, 2026, 05:24 AM UTC

    We are currently investigating this issue.

  2. investigating May 16, 2026, 05:48 AM UTC

    We are continuing to investigate this issue.

  3. monitoring May 16, 2026, 06:09 AM UTC

    A fix has been implemented and we are monitoring that all is back to normal

  4. resolved May 16, 2026, 06:14 AM UTC

    This incident has been resolved.

  5. postmortem May 22, 2026, 01:46 PM UTC

    Incident was caused by a failing maintenance operation that left one of our databases in an inconsistent state. We restored the data and were able to fix the problem. We agreed how to improve the process so that this can be avoided in the future