Edge & TLS
Public routing and encrypted delivery
Freight operations infrastructure
Checking MAFDispatch services
Confirming the application, API, database, and durable job queue.
Not checked yet
Current snapshot
Platform components
Live checks only. No invented uptime percentage.
Application API
Authentication and freight workflows
Data store
Transactional brokerage records
Durable jobs
Queued delivery and background work
Measured availability
30-day service history
Loading independent public HTTPS measurements.
Loading measured service history…
Samples run once per minute from a separate server-side process through public DNS and HTTPS. Coverage is shown separately; missing samples are unknown, never counted as successful. This is application-process-independent same-host monitoring, not geographically independent monitoring.
Public updates
Know when published incidents change.
Subscribe to MAFDispatch-wide public incident updates. Your address is confirmed before delivery and every message includes a direct unsubscribe link.
Checking subscription availability…
Operator-published evidence
Public incident history
Loading the newest public incident page.
Checking the public incident record…
What this page proves
Current health, with deliberate public evidence.
Live health checks come directly from the running MAFDispatch application. Historical availability comes from a separate bounded public-HTTPS probe and reports missing coverage honestly. The complete incident history is available page by page. Entries appear only when a platform operator explicitly marks an all-brokerage incident public. Tenant identities, selected-brokerage incidents, internal notes, provider credentials, and raw diagnostics never enter this page.