Login issue reported, investigation started

Cause identified, fix being applied

All services back to normal

All check-outs appear to be fail during payment.

Issue identified, applying fix

Fix successful, all systems online again.

High error rate in processing IDEAL payments.

Issue identified: Rabobank is facing issues processing IDEAL payments.

IDEAL payments are fully functional again.

All check-outs appear offline.

All check-outs back online.

The sales report function in control panel is not fetching any new data. All other functions are operational.

Root cause of the problem has been identified: slow processing data warehouse.

Hot fix is currently in development. We estimate the sales report coming back online by the end of the day.

Issue has been resolved. All reporting functions are back operational.

Some user activities, such as viewing products, adding items to the cart, or making payments are experiencing errors.

To resolve the issue, our technical team intervened by manually disabling a service that processes background tasks, fixing the task queue and re-enabling the task service. This action helped stabilize the system and restore the smooth operation of services. We are committed to preventing similar occurrences in the future.

We're manually adjusting the scale of the caching service. Systems should be back on track soon.

Systems are now stabilized and operation of services are smooth again. Incident description: During a service disruption, some users might have encountered issues during the checkout process. A significant portion of user activities, such as viewing products, adding items to the cart, or making payments, experienced errors. It is estimated that this affected approximately 8.3% of all requests made within the time period of the disruption. Why did it happen: The service disruption was primarily caused by issues with how our caching service was configured. Certain services were unable to write to the cache as intended, necessitating a direct load of data from the database for each user request. This unexpected burden led to high load levels on our database and subsequent slowdown of services, ultimately causing portion of them to fail.