Visma incident

Winvoice Down

Critical Resolved View vendor source →

Visma experienced a critical incident on September 3, 2026 affecting Winvoice, lasting —. The incident has been resolved; the full update timeline is below.

Started
Sep 03, 2026, 07:48 AM UTC
Resolved
Sep 03, 2026, 07:48 AM UTC
Duration
Detected by Pingoru
Sep 03, 2026, 07:48 AM UTC

Affected components

Winvoice

Update timeline

  1. resolved Sep 03, 2026, 07:48 AM UTC

    Winvoice down due to a certificate management problem in Azure

  2. postmortem Sep 03, 2026, 07:49 AM UTC

    **Issue Overview** Winvoice experienced temporary downtime due to a DNS verification update required for Azure certificate management. **Details & Resolution** Azure required updated DNS records to be set at our domain registrar to complete automated SSL certificate validation. Once our team configured the required records and DNS propagation completed, Azure successfully validated the domain and service access was fully restored. **Next Steps** To prevent similar occurrences, we are migrating our DNS hosting to **Azure DNS Zone** and implementing **Azure Front Door**. This should fully automate our SSL certificate lifecycle management and streamline DNS record management directly within Azure.