Investigating an issue in Visma.net VLS
Incident Report for Visma Cloud Services
Resolved
The issue is now resolved and the service is up and running as normal.
Posted Feb 22, 2021 - 16:30 CET
Monitoring
The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.
Posted Feb 22, 2021 - 15:25 CET
Update
We have identified the cause of the incident and are currently working on finding a solution for this. "Clients (Visma Business, Visma Global ...) using LicenseClientLibrary are affected since some configurations were changed on one of the domain name servers that is hosted by VITC".
Posted Feb 22, 2021 - 15:25 CET
Investigating
We are currently investigating an issue on Visma.net VLS side.
The first checks show affected are on-premise applications like Visma Business, Control, and affected parts are related to licensing methods. We are looking now to find the root cause.
Posted Feb 22, 2021 - 11:12 CET
This incident affected: Visma Mobile Apps (Visma Attach, Visma Scanner, Visma Employee, Visma Manager), Visma Severa / Visma Project Management (Visma Severa / Visma Project Management), Common Services (CS - Visma.net Approval, CS - Visma.net AutoInvoice, CS - Visma.net AutoPay, CS - Visma.net AutoReport, CS - Visma WebInvoice / Visma Webfaktura, Visma Help Centre, CS - Visma Document Storage, Visma.net Payslip, Visma.net Expense), Visma.net Payroll Norway (Visma.net Calendar Time, Visma.net Calendar Absence, Visma.net Calendar Roster, Employee Management), Visma.net ERP (Visma.net ERP, Visma.net ERP API), Visma.net HRM & Payroll Netherlands (Visma.net Payroll), Visma Talent Solutions (Visma EasyCruit), Visma Fivaldi & Visma Payroll Finland (Visma Payroll Finland), and Visma Cloud Platform (CP - Integration Platform, CP - Master Data Management - MDM, CP - Visma Licensing Service - VLS, CP - Message Router, CP - Visma.net Store, Transaction Data Broker).