Previous incidents
The database was busy for a very brief period of time
Resolved Apr 16 at 06:24pm CEST
The database was busy for a very brief period of time. We are already working on optimizing the database usage to make this more efficient and stable in the future.
File server update from cloud platform
Resolved Mar 29 at 11:52am CET
Our cloud platform provider updated the servers on which our websocket application runs.
Hub release
Resolved Feb 26 at 10:52pm CET
This release introduced zero downtime deployments for future Hub releases.
Single instance error
Resolved Feb 23 at 12:00pm CET
One of the instances of our portal was broke. It was recovered by our auto-heal functionality but caused a little downtime on this one instance. The other ones were not affected, so most users won't have notified this problem at all.
A component of the HUB could not start properly
Resolved Feb 09 at 05:01pm CET
After releasing the HUB we noticed that a component did not start. That is why we rolled back the previous version of the HUB which resolved the issue of not being able to perform live authorizations.