All orders are now imported. The issue can be considered as resolved.
May 15, 01:24 CEST
We are working on re-exporting the affected orders.
May 15, 01:13 CEST
We could identify a misbehaving node that caused the activation failures and also the total amount of affected reservations.
The node is up and running again and we'll keep you updated about the import of the orders into the system.
May 15, 00:20 CEST
Since around 9 PM this evening, we noticed an increased amount of failed activation calls, probably caused by a replication error.
We are already investigating and we'll send out further information as soon as we can.
May 14, 23:39 CEST