All posts

When Debitoor had a bad day

Yesterday in the afternoon at 4 pm CET, we acknowledged a failure in a central component in our data infrastructure which caused Debitoor to become unavailable for about an hour.

This meant that if you tried to log on to Debitoor within this timeframe, you probably just saw the page loading in vain.

After service was reinstored, we discovered an issue in our monitoring settings which caused the app to restart periodically.

As a result, you may have experienced issues logging in on an on and off basis for about half an hour after that.

Around 5:30 pm CET, everything was running smoothly and you shouldn’t have experienced any log-in issues after that.

Nighttime downtime

But then, unfortunately, around 11 pm CET, Debitoor ran into a new problem, as the web server security certificate had expired and had to be reactivated, before we could restore service.

If you tried to log on to Debitoor between 11 pm CET and midnight, you saw a message saying that there was a problem with the website certificate.

We found a solution to renew the security certificate around midnight last night, however with the API and the mobile apps unavailable until around 7 am this morning CET.

We deeply apologise if you tried to log on to Debitoor during any of these unrelated incidents and can assure you that no data were affected or insecure in any way during any of these events.