We've now resolved the incident. Thanks for your patience. Sorry for the inconvenience.
Post Mortem: The original issue was caused by a mix of client (mis)configuration (verbose logging) and a too curious bot. As as side effect, a certificate file got corrupted, which caused the load balancer not to reboot correctly. About 50 Apps where affected. Total incident time was about 1.5 hrs. All this time no deployment was possible, in the first half some Apps where offline, in the second half all Apps where offline.
We think to have fixed the issue and are now monitoring the situation.
We are facing some issues. Still looking into it. No ETA yet.
We believe to have found the root of the issue and are working on a fix.
Some apps in US region are having issues with SSH and web delivery. We are working on resolving them.
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.