Visma incident

Degraded performance on API

Minor Resolved View vendor source →

Visma experienced a minor incident on April 28, 2026 affecting Visma Net API, lasting 1h 39m. The incident has been resolved; the full update timeline is below.

Started
Apr 28, 2026, 01:30 PM UTC
Resolved
Apr 28, 2026, 03:10 PM UTC
Duration
1h 39m
Detected by Pingoru
Apr 28, 2026, 01:30 PM UTC

Affected components

Visma Net API

Update timeline

  1. investigating Apr 28, 2026, 01:30 PM UTC

    We are currently investigating this issue.

  2. identified Apr 28, 2026, 02:11 PM UTC

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

  3. resolved Apr 28, 2026, 03:10 PM UTC

    This incident has been resolved.

  4. postmortem Apr 30, 2026, 01:03 PM UTC

    Root cause was a change 10.94.0 related to authentication change where we wanted to optimize the flow of getting authentication tokens from Connect. The goal was to lower the amount of token requests towards Connect and therefore the risk of being throttled. Unfortunately the change led to a locking of threads on some application servers which caused timeouts and degraded performance for some of our customers. We were able to mitigate the problem with a patch by rolling back the change. Monitoring showed that we are back to normal again.