Previous incidents

Instance is recycled and working again.

No real downtime, instance is recycled.

The connection with Hubject was instable due to a technical issue. Our cloud provider helped investigating the issue and proposed some solutions to prevent this in the future.

The service was busy and didn't respond in time, was not a real offline scenario. The delay was caused in a spike of requests.

System needed to be restarted by our cloud provider and caused a moment of delay/downtime.

A release of the hub caused one of the instances to be unstable, disconnected sockets can be a consequence. Issue is resolved.

The performance was poor for a short period of time which caused this downtime.

During a maintenance action, the connect service was not restarted correctly which caused the downtime.

The status on the dashboard is wrongly depicted. We are in discussion with our status page provider and they acknowledged the error.

A reboot of one of our Hubject services caused a couple of minutes downtime.