Public edge health for FleetPath. Honest about what we probe and what we do not.
Public edge: responding
These checks run when this page is loaded (cached at most about one minute). They are outside-in probes, not a full multi-region observability product.
Overall: Public edge surfaces responded successfully.
Page generated at 2026-09-05T00:05:34.796Z (UTC).
Covered by the probes above: the public API edge (including a database reachability signal from the API health payload when present) and the marketing/app website.
Not fully represented here: background workflow workers (may be scaled to zero for cost outside peak use), Tool Gateway and Event Service internal planes, Temporal Cloud, and third-party integrations (ELD, email, maps). Those are operated internally and are not each given a public green light on this page on purpose — we will not invent status we do not probe.
FleetPath does not yet publish a contractual public uptime percentage SLA on this page. Enterprise commitments, if any, live in the customer agreement.
Internal recovery targets under the current backup mode (daily backups; point-in-time recovery deferred for cost) are documented for our compliance program as approximately RPO 24 hours and RTO 4 hours for the primary database path. Those are operational targets, not a customer SLA, until we say otherwise in a signed contract.
If you believe the service is down or you see incorrect data, email admin@fleetpath.app with the time (UTC), what you were doing, and any error text (no passwords or tokens).
We maintain internal incident-response and breach-notification procedures. Security reports: same address, mark the subject clearly.