Visma incident

Cross-Profile Transaction Mix-up in Detect Identified

Critical Resolved View vendor source →
Started
Mar 04, 2026, 12:29 PM UTC
Resolved
Mar 04, 2026, 04:28 PM UTC
Duration
3h 59m
Detected by Pingoru
Mar 04, 2026, 12:29 PM UTC

Affected components

Inyett One

Update timeline

  1. identified Mar 04, 2026, 12:29 PM UTC

    We have identified an issue with indexing related to Detect where transactions from different profiles have been mixed up. We are currently working on a solution to the problem.

  2. identified Mar 04, 2026, 12:42 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Mar 04, 2026, 04:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Mar 04, 2026, 04:21 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 04, 2026, 04:28 PM UTC

    This incident has been resolved.

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