Previous incidents

We tried to release a new version of the hub with stability fixes, but we had to roll back the release due to unforeseen issues. We are planning the new release for next month now.

There was a regular maintenance of our cloud provider causing a little downtime. There is a new release coming which will resolve these kind of issues.

The Portal was released with a newer version but something went wrong in the release process.

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.