Istoricul incidentelor Visma

We experienced stability issues with the Business NXT API this morning. The incident began at 04:56 CET and was fully resolved by 08:35 CET. We apologize for any inconvenience this caused our customers and integration partners.

In the period between 11:45 CET and 12:20 CET the distribution of webhook messages in Business NXT had issues and some webhooks were lost.

Due to a change in configuration and a cached instance our portal (Inyett One) lost communication with one of our backend resources. This was remediated by recreating the instances for the app service that was holding the cached value.

sortering i kurskatalog er feil. Mulig å gjennomføre kurs og søke etter kurs i katalogen. Feilen er lokalisert og under retting.

Feilen er rettet.

We are currently investigating an issue in Spiris Accounting, Invoicing & Payroll, Visma eAccounting, and Visma Administration. At the moment, it is not possible to send e-invoices. We are investigating the issue.

We are still investigating the issue preventing e-invoices from being sent. It is still possible We will update you again as soon as we have any new information.

We are working to resolve the issue as quickly as possible. We will update you again as soon as we have new information.

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

This incident has been resolved.

We are investigating an issue in Approval login

We are working on a fix. For the moment Connect login was disabled in production.

Some features like the Gaia assistant stop working until the fix will be implemented.

The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

Norsk: Driftsforstyrrelser på AWS WorkSpaces Status: Utfordringer med AWS WorkSpaces Vi opplever for øyeblikket tekniske problemer som påvirker AWS WorkSpaces. Visma jobber nå for fullt med å finne årsaken og rette feilen så raskt som overhodet mulig. Vi beklager virkelig ulempene dette medfører for arbeidsdagen din. Vi kommer med en ny oppdatering så snart vi har mer informasjon å dele. Takk for tålmodigheten! English: Service Disruption on AWS WorkSpaces Status: Issues affecting AWS WorkSpaces We are currently experiencing technical difficulties affecting AWS WorkSpaces. Visma is actively working to identify the root cause and resolve the issue as quickly as possible. We sincerely apologize for the inconvenience this causes to your workday. We will provide an update as soon as more information becomes available. Thank you for your patience!

Norsk: Vi kan bekrefte at problemet med AWS WorkSpaces er identifisert og utbedret. Årsaken til driftsforstyrrelsene var et tegn i en databasetabell som inneholder brukerinformasjon, og som ikke støttes av systemet. Dette førte til at AWS WorkSpaces ikke fungerte som forventet. Rettingen er bekreftet gjennomført, og tjenesten skal nå fungere normalt. Vi anbefaler at du prøver å logge inn på nytt dersom du fortsatt opplever problemer. Tiltak er allerede iverksatt for å forhindre at tilsvarende hendelse skjer igjen. Vi beklager ulempene dette har medført og takker for tålmodigheten. English: We can confirm that the issue affecting AWS WorkSpaces has been identified and resolved. The root cause was an unsupported character present in a database table containing user information, which caused AWS WorkSpaces to malfunction. The fix has been applied and confirmed, and the service should now be operating normally. If you are still experiencing issues, we recommend signing out and signing back in. Measures have already been put in place to prevent this from happening again. We apologize for the disruption to your workday and thank you for your patience.

We are currently investigating an issue in Visma Recruit.

In Swedish; Vi tror att vi har identifierat orsaken till incidenten, som är kopplad till dagens release. Vi arbetar för närvarande med att ta fram en lösning och återkommer med en ny statusuppdatering så snart vi har mer information. Vi beklagar besväret. In English; We believe we have identified the cause of the incident, which is related to today's release. We are currently working on a solution and will provide a status update as soon as we have more information. We apologize for the inconvenience.

På svenska: Tjänsten är åter i full drift och problemet ska nu vara löst för samtliga kunder. Vi övervakar systemet noggrant under den närmaste tiden för att säkerställa stabil drift och hög kvalitet. In English: The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.

Driftstörningen är nu helt löst och Visma Recruit är i normal drift sedan klockan 19:00. Vi tackar för ert tålamod under tiden vi arbetade med att åtgärda felet! In English: The issue is now fully resolved and Visma Recruit has been running as normal since 19:00. Thank you for your patience while we worked to resolve this issue!

We are investigating issues with document downloads and degraded performance.

This incident has been resolved.

We are currently looking into performance degradation in Payroll.

We've deployed fixes to address the degraded performance and the service is now operating normally. We'll continue to monitor to confirm full resolution.

This incident has been resolved.

We are experiencing unusual slowness, we are investigating.

We are continuing to investigate this issue.

This incident has been resolved.

The issue has been identified.

This incident has been resolved.

We are currently investigating an issue in Business NXT API. Some mutations do not return a result even if they are executed successfully. Reading operations are working as expected. We will be back with more information shortly.

The service is up and running again. This issue should be solved for all customers. We will keep monitoring to ensure high quality.

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

We're experiencing again slowness in all our Applications We're looking into the issue as we speak

High response time seems to be due to high load on a network shared resource we're using with other projects. Network team will undergo an emergency maintenance window to increase resources on that infrastructure in order to handle more load during red periods. Emergency Maintenance will happen soon, when everything will be settled time will as well be announced

Emergency change has been implemented, server resources seem to handle better the load, we're now monitoring the results and if all our infrastructure goes back to normal behaviour

We are continuing to monitor for any further issues.

This incident has been resolved.

We're experiencing high response time on all our infrastructure, we're investigating to track the root cause

Applications seems to be back to normal, also our monitoring is looking fine. We are investigating with networking team to find root cause which is yet not known We'll be monitoring our apps in case this happens again

We'll mark the incident as resolved as platform seems to be stable now and no more issues reported, still we're aware that this problem might reappear in the future, but some followup actions are ready to be taken if so

We are currently investigating this issue.

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

This incident has been resolved.

We are currently experiencing problems in Maventa service, starting Friday 2026-05-29 14:00 UTC and still ongoing. The issues are causing: - Delays in importing incoming invoices and documents from Peppol - Delays in sending invoices - Timeouts on API (especially lookup methods) - Timeouts on Maventa UI Finder We are currently investigating these issues.

A fix has been implemented at 12:22 UTC and we are monitoring the situation

This incident has been resolved.

We have identified the cause of the incident and are currently working on finding a solution for this. The error blocks our Customer invoices flow. This impacts users of Inexchange and Hubix.

The service is up and running again for new invoices. This issue should be solved for all customers sending new Customer invoices. We will keep monitoring to ensure high quality.

We are continuing to monitor for any further issues.

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