Visma incident

Investigating an issue in Hubix

Critical Resolved View vendor source →

Visma experienced a critical incident on February 9, 2026 affecting InExchange and Hubix, lasting 28m. The incident has been resolved; the full update timeline is below.

Started
Feb 09, 2026, 08:21 AM UTC
Resolved
Feb 09, 2026, 08:49 AM UTC
Duration
28m
Detected by Pingoru
Feb 09, 2026, 08:21 AM UTC

Affected components

InExchangeHubix

Update timeline

  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.