Visma Outage History

Visma.net ERP API experienced degraded performance for 35 minutes on March 13, 2026. The issue affected API functionality for the ERP system and was resolved after investigation.

Visma's Enterprise Plus service experienced degraded performance for 2.3 hours. The issue was identified and a fix was implemented, with monitoring confirming the resolution. The incident has been fully resolved.

Visma's Detect service experienced a major indexing issue where transactions from different user profiles were incorrectly mixed up with each other. This cross-profile data mixing affected transaction visibility and accuracy for users accessing the Detect functionality. The issue was resolved after 4.1 hours with a fix implementation followed by monitoring to ensure stability.

Visma's My Services and connected services experienced degraded performance affecting the CP - Visma Online component for 3.7 hours. The issue was identified and performance was restored to normal levels. The incident was fully resolved with service performance returning to expected levels.

Visma HoP experienced a major incident affecting electronic document signing functionality that lasted 49.3 hours. The Visma Signature service was impacted, preventing users from signing documents electronically. A fix was implemented and monitored before the incident was fully resolved.

Visma Severa and Visma Project Management experienced slowness issues that lasted 8.6 hours. The engineering team investigated the problem and implemented a fix. The incident was resolved after a monitoring period to ensure stability.

Visma Net ERP customers experienced general slowness across the system for approximately 67.6 hours. The issue was resolved through system changes and server recycling, which restored normal performance for most customers. The incident was fully resolved after a monitoring period to ensure stability.

Visma experienced intermittent challenges with invoice processing and billing that affected the Enterprise Plus component for 21.6 hours. The service provider worked to identify the root cause of the problem while users encountered disruptions to their billing operations. The issue was resolved after investigation and remediation efforts.

Maventa experienced degraded performance with increased failure rates and timeouts, affecting the CS - Visma.net AutoInvoice component. The incident lasted 45.4 hours, requiring multiple fix attempts before the root cause was properly identified and resolved. The issue was fully resolved after implementing a successful fix and monitoring period.