Visma outage history

Winvoice down due to a certificate management problem in Azure

**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.

Accounting documents is currently experiencing a major outage. Our team is investigating the issue.

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

We are currently investigating this issue.

This incident has been resolved.

Driftsavvik: Ustabilitet på Amazon WorkSpaces Applications Vi opplever for øyeblikket teknisk ustabilitet på Amazon WorkSpaces Applications. Status: Teknisk team jobber for fullt med å feilsøke og utbedre problemet. Konsekvens: Brukere kan oppleve treghet, feilmeldinger eller utfordringer med å koble til sesjoner. Vi beklager ulempene dette medfører, og kommer med en ny oppdatering så snart vi har mer informasjon. Service Alert: Amazon WorkSpaces Applications Instability We are currently experiencing technical instability with Amazon WorkSpaces Applications. Status: Our technical team is actively investigating and working to resolve the issue. Impact: Users may experience slowness, error messages, or trouble connecting to sessions. We apologize for any inconvenience and will share an update as soon as more information is available.

We are continuing to investigate this issue.

Problemene har blitt identifisert, og vi jobber med å løse de.

Vi har funnet problemet, og monitorerer saken.

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.

Stability is currently experiencing a major outage. Our team is investigating the issue.

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

Marketplace is currently experiencing a major outage. Our team is investigating the issue.

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

Integretionmicrosoft365 is currently experiencing a major outage. Our team is investigating the issue.

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

Interco is currently experiencing a major outage. Our team is investigating the issue.

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

Billing is currently experiencing a major outage. Our team is investigating the issue.

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

Archive is currently experiencing a major outage. Our team is investigating the issue.

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

Accounting module is currently experiencing a major outage. Our team is investigating the issue.

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

Inqom Api is currently experiencing a major outage. Our team is investigating the issue.

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

Revision is currently experiencing a major outage. Our team is investigating the issue.

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

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

The issue is identified - not enough GPU resources.

We are continuing to work on a fix for this issue.

Smartscan is stabilising, we continue to monitor the situation

This incident has been resolved.

We are currently experiencing degraded performance affecting HoP authentication and DLP functionality. Our team is actively investigating the issue and working to restore full service as quickly as possible. We will provide updates as more information becomes available.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We see degraded performance on UI and API. Also on Visma Approval is affected.

We are continuing to work on a fix for this issue.

We are implementing a fix at the moment. Estimated time to production is 2 hours.

Fix has been verified and will be deployed to production in 15 minutes.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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.

Vi gjør oppmerksom på at Id-Porten fremdeles har tekniske utfordringer, noe som kan medføre innloggingsproblemer i Enterprise Plus og Visma Enterprise Ressursstyring Plus. Status: Teknisk team jobber fortløpende med å løse saken. Konsekvens: Innlogging på løsningene kan mislykkes eller ta lengre tid enn normalt. Vi beklager ulempene dette medfører, og oppdaterer så snart situasjonen er løst. Takk for tålmodigheten! Please be advised that Id-Porten is still experiencing technical difficulties, which may cause login issues for Enterprise Plus and Visma Enterprise Ressursstyring Plus. Status: The technical team is actively working to resolve the issue. Impact: Logging in to the solutions may fail or take longer than usual. We apologize for any inconvenience this may cause and will provide an update as soon as the situation is resolved. Thank you for your patience!

We are continuing to investigate this issue.

Status 09:00 Det tyder på at angrepet er avsluttet. Våre løsninger har fungert i stor grad som normalt gjennom natten, og trafikken tar seg opp på vanlig måte utover dagen. Det er kun noe trafikk fra utlandet som fortsatt har hatt driftsforstyrrelser som følge av angrepet. Vi har beholdt beredskapstiltakene gjennom natten som en forsikring, og følger situasjonen videre utover dagen. Angrepet startet natt til mandag kl. 03.38 og stoppet ved 19.30-tiden onsdag kveld. Med unntak av korte perioder har ID-porten og fellesløsningene vært tilgjengelige hele tiden. Vi forventer å komme over til normal drift i løpet av de nærmeste dagene.

This incident has been resolved.

The Norwegian Peppol SMP Elma is having an incident: https://status.digdir.no/incidents/d7tgwqgzd742 This causes delays in invoice deliveries in Maventa and failures (lookup_retry_error) in lookups.

Issues seem to be resolved at Elma SMP - no delays currently

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

We have an issue with synchronization between services (Approval and Admin) and Business NXT. The issues should be fixed, but there is some delay while synchronization processes the queue that has built up. We will keep monitoring and ensure everything works as expected.

The issue is now resolved and the service is up and running as normal.