Published analysis is derived from the maintained route registry rather than the larger compatibility/archive surface. The compact runtime and curated registry are required to remain row-identical before Phoenix update installers proceed.
Research object and source snapshot
The current public research program is built from Phoenix Auto Dispatch's maintained 579-route planning dataset. The downloadable snapshot used by the published 2026 analysis is dated August 28, 2026. Each maintained record represents a Phoenix planning connection retained in the site's curated route graph; it is not a shipment ledger.
Core definitions
| Maintained route | A route connection intentionally retained in Phoenix's curated public planning graph at the time of the snapshot. |
|---|---|
| Directional route | One origin-to-destination record. If the reverse direction is separately maintained, it is a separate directional record. |
| Endpoint city | A city appearing as the origin or destination of at least one maintained directional route. |
| Connected state | A state or state-equivalent reached by at least one maintained route connection in the relevant profile. |
| Planning distance | The maintained route-distance value used for site planning and comparative analysis. It should not be interpreted as a guaranteed carrier mileage, invoice mileage or exact driven path. |
| Median planning distance | The middle planning-distance value after the applicable maintained records are ordered by distance; it describes this dataset, not all U.S. vehicle shipments. |
| Connectivity | The number or pattern of maintained planning links involving an endpoint. Connectivity is not customer demand, shipment popularity or market share. |
What enters the analysis
State and city research profiles aggregate only maintained records that actually touch the applicable geography. A geography with no direct maintained route evidence does not receive invented route statistics.
Route connectivity may be used as geography-planning context on service pages, but Phoenix does not treat those route records as proof that a particular service type was purchased or completed on those routes.
What the dataset does not measure
Important limitation: Phoenix's route graph does not establish completed shipment volume, customer demand, popularity, market share, current quote prices, live carrier capacity, on-time performance, review sentiment, regulatory authority or a delivery guarantee. It also does not prove that a displayed service category was used for any maintained route.
Reproducibility and verification
Readers can reproduce or challenge Phoenix's published aggregate statements by downloading the cited CSV snapshot and applying the definitions on this page. The public analysis and visual assets are derived from that maintained research program. When Phoenix publishes a materially changed snapshot, the appropriate research pages should identify the new version/date rather than silently representing an older snapshot as current.
Corrections, reuse and citation
For citation guidance, publisher-ready company facts or questions about a source definition, use the resources below. Independent publishers retain editorial control; linking to or citing Phoenix does not establish endorsement, affiliation or partnership.
Factual correction requests may be sent to INFO@PHOENIXAUTODISPATCH.COM.