Resolved -
We've restored 100% accounts. Right now, we are monitoring systems.
Nov 19, 16:52 CET
Update -
We've restored 100% of accounts in the US and ASIA regions and are consequently restoring the data for clients in the EU. Currently, we've fixed approximately 80% of affected accounts in EU.
Nov 19, 09:30 CET
Update -
We are consequently restoring the data. Currently, we've fixed approximately 50% of affected accounts.
Nov 18, 17:08 CET
Update -
We are consequently restoring the data. Currently, we've fixed approximately 25% of affected accounts.
Nov 18, 15:06 CET
Update -
We are consequently restoring the data. Currently, we've fixed approximately 15% of affected accounts. The ETA for correcting balances will take longer than we expected.
Nov 18, 13:33 CET
Update -
We are consequently restoring the data from the moment before our last release. The ETA for correcting balances in all accounts is 60-90 minutes.
Nov 18, 12:46 CET
Monitoring -
We are consequently restoring the data from the moment before our last release. The process of restoring the data is in the production environment. Carry-over balances will be fixed in the next 30-60 min for the first group of our clients.
Nov 18, 11:38 CET
Update -
We've found a solution to prevent the problem from spreading—it is currently rolling out to the production environment. We are still working on a solution for recalculating carry-over to the correct amount.
Nov 18, 10:46 CET
Update -
We are working on a solution to ensure the consistency of all our clients' data. We still do not have an ETA for solving the problem, but we will let you know as soon as we find one.
Nov 18, 10:23 CET
Identified -
We found the cause of the issue and are working on a solution. The problem is related to our recent release - improvements in the carry-over engine.
Nov 18, 09:50 CET
Investigating -
We are currently investigating the issue.
Nov 18, 02:00 CET