We've experienced a higher CPU than usual load on the Git node starting this morning around 4am (UTC). The load itself was not a dramatic issue, since this is caused (and expected) by extensive post-deploy scripts which run in parallel. However, the availability of the node continued to decrease till it was around 9am (UTC) completely unavailable.
At that time, we replaced the node with a new one, which is since available. Note: The IP address of the node has changed, so you might be informed (by your Git/SSH client) about a possible man-in-the-middle attack. This can be safely ignored (in this case). Follow the instructions of your client and remove the old fingerprint from your known-hosts file.
This incident has been resolved.
One git node (git8) is not responsive at the moment. We are currently looking into the issue.
We’ll find your subscription and send you a link to login to manage your preferences.
We’ve found your existing subscription and have emailed you a secure link to manage your preferences.
We’ll use your email to save your preferences so you can update them later.
Subscribe to other services using the bell icon on the subscribe button on the status page.
You’ll no long receive any status updates from fortrabbit, are you sure?
{{ error }}
We’ll no longer send you any status updates about fortrabbit.