We are currently investigating an incident where the underlying resources used by the platform are unavailable, slow to respond and/or moving.
The effect is primarly related to our backend resources, indirectly affecting the API and the Merchant/Self-Service.
We are monitoring the issue, and have started investigations with Microsoft Support, as well as provisioned additional resources to mitigate the issue.
From 03:00 to 09:30 CET we had problems importing payments from file. This was due to an error in the configuration, but it has now been fixed.
Due to system upgrade, the production environment had an invalid configuration for the OAuth audience. This caused several requests to fail as they were rejected as unauthorized. Requests to the API were also affected.
Starting 22nd October, we have experienced some operational problems related to payment agreements. The issue has affected new orders and all requests for information on payment agreements.
We have rectified the issue, and are currently working the list of orders that have failed in an attempt to recover them. We are still investigating the root cause.
Some users may have experienced reduced performance today. We are now investigating to find the cause. We apologize if this creates any issues
We are now experiencing some operational problems related to payment agreements: Some of the problems concern OCR imports and the creation of new agreements.
We are working hard to correct mistakes. We apologize for any inconvenience this may cause.
Due to a misconfiguration during version upgrade, some users experienced problems during order registration in the period 04:19 to 09:30 CET.
Har du en RSS utvidelse eller ønsker at nettleseren varsler deg om Driftsmeldinger fra oss.Abonnér