What this page checks. Each line below is resolved from live
configuration when you load the page - whether a component has what it needs to work at all. It is not
uptime monitoring: there are no response-time figures and no uptime history here, because we do not
measure them yet and would rather show nothing than numbers we cannot stand behind.
"Not monitored" means the component is serving but nothing is
watching it.
Website
Serving this page; no external health check is wired yet.
Not monitored Authentication
No Basefyio anon key configured — sign-in cannot work.
Outage Account & plan store
No Basefyio anon key configured — every database-backed page fails.
Outage Load board
No live load supply is connected. Postings are generated on real lanes and real registered carriers, and the board says so on the page.
Degraded Rate engine
UBER_MOCK is on, so quotes are priced by the local rules engine rather than the contracted API.
Degraded Booking & tender
UBER_MOCK is on — a tender is recorded locally and no load is offered to a real carrier.
Degraded Shipment tracking
No contracted visibility provider. References outside a booking we placed resolve to a mock timeline, stamped meta.mode "mock" on every response.
Degraded Tracking webhook
No callback secret configured — the endpoint refuses every push, so status is only refreshed on demand.
Degraded Carrier directory
Served from the in-repo registry — 38 registered carriers. No upstream needed.
Operational Depot & metro directory
Served from the in-repo dataset — 138 depots. No upstream needed.
Operational Tools & calculators
Distance, load and cost tools compute locally.
Operational Email delivery
No provider configured — no email is sent: not verification, password reset, booking acknowledgements or operator alerts. Each dropped message is logged as an error on the server.
Outage Operator booking alerts
No email provider, so new bookings and quote requests alert nobody. They are saved and listed in the operator inbox.
Outage Verification & reset links
No signing secret on this deployment — reset links would be forgeable, so signing refuses outright.
Outage Embed tokens
SESSION_SECRET is unset on this deployment, so the endpoints refuse to sign rather than use a key from the repository.
Outage Uptime history
There is no uptime chart on this page. The one that used to be here drew 90 bars from a counter, and
the two amber days in it were decoration - they moved with the page, not with any incident.
Response-time probes and uptime sampling start with the public API, and this page will show measured
history from that point forward, not a back-filled estimate.
Something broken that this page says is fine?
Tell us - a status page that
disagrees with reality is a bug in itself.