Visma Outage History

Visma experienced a major network issue that made all Flyt Common solutions unavailable for 18.5 hours, affecting Visma Flyt PPT, Visma Flyt BVV, Visma Flyt Omsorg, and Visma Flyt Sikker Sak. The issue was identified and a fix was implemented, followed by a monitoring period before full resolution was confirmed.

Visma HoP experienced a partial outage affecting the Visma Signature service for 2.1 hours. Users were unable to access signature functionality during this period. The incident was resolved after investigation and remediation efforts.

Visma.net ERP experienced a major login issue that prevented users from accessing the system for 4 hours. The problem was identified and a fix was implemented, with the service being monitored before full resolution. The incident was resolved after the fix proved successful.

Visma's HRM Analytics service in the Netherlands experienced a major outage lasting 101.6 hours due to problems with their generic API that caused timeouts for customers. The issue was traced to problems with the datawarehouse delivering data, with Amazon Redshift assisting in finding the root cause. The service was fully restored on March 23rd after API functionality was recovered and reporting data was refreshed.

Some customers experienced access issues to their companies in Visma's Skatt & Bokslut service, receiving maintenance messages when attempting to log in. The major incident lasted approximately 10 days before a fix was implemented and monitored. The issue was fully resolved after the monitoring period confirmed the solution was working properly.

Visma experienced a major synchronization issue between Webfaktura (WebInvoice) and Business NXT that lasted 76.8 hours. The root cause was identified and a fix was developed and deployed. The service was fully restored and returned to normal operation after a monitoring period to ensure stability.

Visma experienced a major service incident where requests from Valu8 were failing. The issue affected integration functionality between the two systems for 33 minutes. The incident was resolved after investigation and remediation efforts.

Visma experienced payroll login issues that prevented users from accessing Visma.net Absence, Employee Management, Time, and Roster components for 1.1 hours. The company implemented a fix and monitored the system before confirming full resolution of the incident.

Visma.net Platform experienced a major issue with its Identity server component (IDS) that prevented users from logging in and accessing applications. The incident affected the Visma.net ODP component and lasted 1.4 hours before being resolved with a fix implementation and monitoring period.

Visma experienced a major issue with Plandisc on create.plandisc.com that lasted 2.6 hours. The service was restored and monitored to ensure stability before being fully resolved. All customers were affected by the outage until the service returned to normal operation.