Visma Cloud Services Incident History

1. resolvedSep 17 · 12:19 UTC

   This incident has been resolved.

Reported by Visma Cloud Services on their status page.

1. resolvedSep 14 · 09:54 UTC

   The incident affecting Inqom Api has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedSep 14 · 09:52 UTC

   The incident affecting Accounting module has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedSep 14 · 09:42 UTC

   The incident affecting Inqom Api has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedSep 11 · 09:29 UTC

   The incident affecting Fscp has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedSep 11 · 08:59 UTC

   This incident has been resolved.

Reported by Visma Cloud Services on their status page.

1. postmortemSep 3 · 07:49 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.

Reported by Visma Cloud Services on their status page.

1. resolvedSep 1 · 20:28 UTC

   The incident affecting Accounting documents has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 31 · 20:37 UTC

   This incident has been resolved.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 31 · 12:44 UTC

   Vi har nå lagt ut en rettelse som skal løse problemet der basismodul-ikonene på startsiden ikke ga noe svar, eller ga en feilmelding, når de ble åpnet.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 02:31 UTC

   The incident affecting Stability has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 02:32 UTC

   The incident affecting Marketplace has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 02:32 UTC

   The incident affecting Integretionmicrosoft365 has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 02:33 UTC

   The incident affecting Interco has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 05:38 UTC

   The incident affecting Billing has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 02:33 UTC

   The incident affecting Archive has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 03:34 UTC

   The incident affecting Accounting module has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 03:34 UTC

   The incident affecting Inqom Api has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 30 · 05:37 UTC

   The incident affecting Revision has been resolved. We will keep monitoring to ensure everything remains stable.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 27 · 14:58 UTC

   This incident has been resolved.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 26 · 12:35 UTC

   This incident has been resolved.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 26 · 11:55 UTC

   This incident has been resolved.

Reported by Visma Cloud Services on their status page.

1. postmortemAug 28 · 09:47 UTC

   In 11.0.9.version we released an improvement for memory handling to be able to scale workload in a more efficient way. This was tested in our test environments but no issues were found. After releasing 11.0.9. we monitored the solution and noticed that the application servers were not performing as expected and processes were taking too long to complete and were timing out. Very soon we concluded on the root cause and decided to release a patch version which fixed the issue. We will add a mechanism to prevent processes to run too long on the servers and to prevent integrations to trigger the same process again in case we have a similar issue. This will stop the problem from escalating. We have also agreed on a process that should be followed with similar changes so that we are more aware of the risk and are able to notice it earlier in the development process.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 27 · 11:24 UTC

   This incident has been resolved.

Reported by Visma Cloud Services on their status page.

1. resolvedAug 24 · 10:05 UTC

   Issues with the Norwegian Peppol SMP Elma resolved at Digdir side.

Reported by Visma Cloud Services on their status page.