FloraPass status

This page is hosted on a separate server from the FloraPass application itself, on purpose -- so it stays reachable even when the application is not.

✅ All systems operating normally

Last updated: 2026-08-15 12:00 UTC — this line is updated by hand during an incident. If the timestamp above looks old, treat it as stale and unverified rather than as reassurance that nothing is wrong.

What this means

FloraPass runs as a single application instance in a single hosting region, with no uptime commitment and no service level agreement. This is a deliberate, costed posture, not an oversight -- an outage shows up here as an interruption to be recovered from, not as a breach of a promise that was never made. In a real incident, recovery is a best effort: the operational recovery targets below are measured or transparently derived where they can't be, and are not a contractual commitment.

Application outage, data intact: a redeploy onto a surviving server is typically well under a minute of active work (measured from 5 real deploys: 20-39 seconds), plus whatever DNS or queueing delay applies on the day.
Application server lost outright: rebuilding from nothing is dominated by DNS propagation time at the domain registrar, not by the rebuild steps themselves -- this can range from minutes to the better part of a day depending on how the DNS record is configured.
Database recovery point: continuous write-ahead-log archiving bounds data loss to roughly 60 seconds, not the once-a-night backup cadence.

The database, the application server and this status page all run in the same hosting provider and the same region. A large enough event in that region can affect the application, its data, and this page together -- this page cannot promise otherwise.

More information

FloraPass — this page is served independently of the application and is updated manually.