What this page checks. Each line below is resolved when you load
the page, from live configuration and from the dataset on disk — 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 Accounts & sign-in
Basefyio is not configured (Missing: BASEFYIO_API_URL, PUBLIC_BASEFYIO_ANON_KEY, BASEFYIO_KEYCLOAK_REALM, BASEFYIO_SERVICE_KEY.) Sign-in fails closed.
Outage Account register
Not probed: Basefyio is not configured.
Outage Workspace store
Unlocks, claims, bookings and quote requests are held in JSON files on the application server. There is no database behind them, so they do not survive a redeploy onto fresh storage and do not replicate across instances.
Degraded Forwarder directory
The processed dataset is missing from disk — the directory, search, unlocks and exports all have nothing to read.
Outage Data pipeline
The harvester runs outside this process and no dataset build is present on disk.
Not monitored Contact unlocks
No dataset on disk, so there are no contacts to unlock.
Outage CSV export
No dataset on disk, so an export would have nothing to write.
Outage Quote requests (RFQ)
A request is matched against the directory and stored, and the operator and the customer are emailed a copy when email is configured. No forwarder is contacted — there is no channel to them.
Degraded Indicative rates
Rate figures are generated from a local model, not sourced from carriers or forwarders. The rates page says so; they are a planning guide, not a quote.
Degraded Shipment tracking
No carrier or visibility integration. Only the demonstration references listed on the tracking page resolve, and the page names them.
Degraded Email delivery
No email provider is configured (SMTP_URL unset or not a usable SMTP URL), so no email is sent. Each attempt is recorded in the operator email log as not sent. Sign-up confirmation is sent by Basefyio.
Outage Scheduled jobs
No CRON_SECRET configured — the scheduled endpoints reject every trigger.
Degraded Listing re-verification
No verification source is configured, so listings are not re-verified. Each listing shows the verification date its source register gives, or none; nothing marks a listing verified without a check.
Outage Uptime history
There is no uptime chart on this page. The one that used to be here drew ninety identical green bars
from a counter — it had no input at all, so it would have stayed green through any outage.
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.