fortrabbit Outage History

fortrabbit is up right now

fortrabbit had 5 outages in the last 2 years totaling 359h 55m of downtime — averaging 0.2 incidents per month.

There were 5 fortrabbit outages since September 18, 2025 totaling 359h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fortrabbit.com/

Minor June 2, 2026

TLS certificate issues

Detected by Pingoru
Jun 02, 2026, 08:41 AM UTC
Resolved
Jun 02, 2026, 12:11 PM UTC
Duration
3h 30m
Affected: US (US Pro Apps)US (US Universal Apps)EU (EU Pro Apps)EU (EU Universal Apps)
Timeline · 2 updates
  1. investigating Jun 02, 2026, 08:41 AM UTC

    We are looking into issues for Let's Encrypt certificates that have been recently created or renewed.

  2. resolved Jun 02, 2026, 12:11 PM UTC

    We think to have resolved the certificate issue. It was related to a change in Let's Encrypt root chain certificate. This is something, that is not happening on a regular basis, so it was not included with general security monitoring of external sources. It affected only a small number of newly created or recently updated certificates. Contact us if you still see SSL issues.

Read the full incident report →

Major April 21, 2026

Website screenshots unavailable for old dashboard

Detected by Pingoru
Apr 21, 2026, 10:44 AM UTC
Resolved
May 05, 2026, 08:05 PM UTC
Duration
14d 9h
Timeline · 1 update
  1. investigating Apr 21, 2026, 10:44 AM UTC

    The App website screenshots in the dashboard are currently broken, always returning an image of a standard 404 error. As we planned to introduce website screenshots for the new platform as well soon, we plan to have the new websites screenshot service to serve both platforms, new and old. Until then, please allow us to not serve website screenshots. We hope to have website screenshots for new and old platform back in May.

Read the full incident report →

Major September 18, 2025

Web delivery and SSH connection issues

Detected by Pingoru
Sep 18, 2025, 06:05 PM UTC
Resolved
Sep 18, 2025, 07:29 PM UTC
Duration
1h 23m
Timeline · 1 update
  1. resolved Sep 18, 2025, 07:29 PM UTC

    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.

Read the full incident report →