Visma Outage History

Visma's AutoReport service experienced degraded performance for 2.1 hours on April 16th, 2026. The CS - Visma.net AutoReport component was affected, causing reduced functionality for users. The issue was identified, a fix was implemented and monitored, and the incident was fully resolved.

Visma.net Payroll experienced a major partial outage that lasted 50 minutes. The incident was identified and a fix was implemented, with full service restoration completed. The outage affected payroll functionality within the Visma.net platform.

Visma experienced a major incident where users were unable to register claims in the Expense service. The issue affected the Visma.net Expense component and prevented normal expense claim submission functionality. The problem was resolved after 8 minutes, restoring the ability to register claims.

Visma experienced outgoing email sending issues affecting Visma Horizon, Visma HoP, and Numo services for 3.6 hours. The cause was identified and the team worked on implementing a solution. Email sending functionality was fully restored across all affected services.

The GAiA Assistant chat feature in Visma experienced a major outage that prevented users from accessing the chat functionality. The incident lasted 18.2 hours, during which the development team identified the root cause and implemented a fix. The service was fully restored and confirmed working after a monitoring period.

Visma.Net Calendar experienced delays that affected the Time and Absence components for 1.8 hours. The technical team identified the root cause and implemented a fix, though some system delays persisted during the recovery period. The service was fully restored to normal operation after monitoring confirmed the delays had been resolved.

Visma experienced cloud infrastructure instability where new server nodes were failing to deploy randomly, causing degraded performance for Visma.net ERP and its API. The issue was investigated in collaboration with the cloud provider, and a fix was implemented and monitored before the incident was resolved after 1.7 hours.

Visma WebInvoice/Webfaktura experienced a major synchronization issue that lasted approximately 6 days (145.9 hours). The root cause was identified and a fix was developed and deployed. The service was restored to normal operation and monitored to ensure stability before the incident was fully resolved.

Visma experienced a major login issue with their Approval service that prevented users from accessing the system. The incident was resolved by temporarily disabling Connect login in production while implementing a fix. The service was restored after 2.3 hours with continued monitoring to ensure stability.

Visma's Enterprise Plus service experienced an 11.4-hour outage affecting several web applications due to infrastructure limits being reached. The company identified the root cause, implemented a solution, and restored services. All Enterprise Plus customers were impacted during this major incident.