Visma Outage History

Visma experienced a major incident where approval requests were failing in the CS - Visma.net Approval component. The issue was investigated, a fix was implemented, and the incident was resolved after 8 minutes of downtime.

Visma.net Payroll experienced slowness issues that lasted 9.4 hours. The incident was classified as minor and affected system performance. The issue was resolved after investigation and monitoring confirmed that performance returned to normal levels.

Some Visma.net ERP customers experienced slower performance for 3.4 hours due to one customer making excessive API calls on a shared server. The issue was resolved by upscaling server resources and addressing the problematic API usage with the affected customer. Performance returned to normal and the incident was fully resolved after monitoring.

Visma Net ERP experienced an issue where not all incoming invoices were arriving from AutoInvoice, preventing complete invoice processing. The problem affected the Visma.net ERP component for 2.6 hours. The issue was identified and fixed, with invoice reception restored to normal operation.

Visma experienced a major login problem affecting IM web and Control Edge services for 1.4 hours. A fix was implemented and monitored before the incident was fully resolved. Users were unable to access these platforms during the outage period.

Visma experienced slow performance issues in their Calendar service, which affected Visma.net Absence, Visma.net Time, and Visma.net Roster components for 3.3 hours. The issue was investigated and monitored before being fully resolved, with all services returning to normal operation.

Visma experienced a major outage affecting access to the start page and Enterprise Plus functionality for 2.5 hours. Users encountered "Service Unavailable" errors and were unable to retrieve tasks from HRM, including invoices and e-vouchers, causing disruption to their workday. The technical team resolved the issues and restored full service, while implementing additional system improvements to prevent future occurrences.

Visma experienced technical challenges affecting the Startpage for some customers using Enterprise Plus services, lasting 1.6 hours. The engineering team identified the root cause and deployed a fix to restore full access for all customers. The service was fully restored with additional system improvements implemented to prevent future occurrences.

Visma Directe Bankkoppeling experienced issues retrieving data from the Chamber of Commerce, preventing customers from connecting new bank accounts via PSD2-connections and displaying Chamber of Commerce unavailability errors. Existing connected bank accounts remained unaffected throughout the incident. The issue was resolved after 18.4 hours through collaboration with the Chamber of Commerce.

Visma's AccountView.Net service experienced an issue where customers encountered errors when trying to search in the Chamber of Commerce. The problem affected the CS - AccountView.Net component and required collaboration with the Chamber of Commerce to resolve. The issue was resolved after 18.5 hours, restoring normal service functionality.