Skip to main content
24/7(239) 526-873324/7

How long does a CDLIS query take?

A CDLIS pointer query typically returns inside 5 to 15 seconds during AAMVA system hours. The pointer record (every state where the driver has held a CDL since 1996) is real-time. State-of-record detail pulls fan out from the pointer and run in parallel, so the total round-trip on a multi-state CDL driver rarely exceeds 60 seconds.

CDLIS is a federally-managed pointer database operated by AAMVA under FMCSA contract. The §384.225 regulation requires every state DMV to push CDL events to CDLIS within 10 days of the underlying state action, so the pointer record is current to within a 10-day window for every state in the system. Real-time queries against the pointer return the index in seconds — the architecture is read-fast by design.

A typical CDLIS query returns three items: (1) a list of every state where the driver has held a CDL since 1996, (2) issuance and termination dates for each state of record, and (3) the federal CDLIS-derived driver number used to cross-link the records. The pointer itself is the AAMVA index; for the underlying detail (license class, endorsements, restrictions, current license status, conviction history), the carrier still pulls a state MVR from each listed state.

CDLIS uptime is publicly tracked at the AAMVA system-status board (https://www.aamva.org/Status/). The pointer service is generally available 24/7 with rare maintenance windows announced 24-48 hours in advance. State-DMV detail pulls follow each state's own DMV uptime — the slowest state in the fan-out sets the total return time on a multi-state CDL driver.

For the bundled DOT Pre-Employment package, CDLIS is rarely the bottleneck — MVRs from any batch state in the fan-out usually take longer. The total bundled return time during business hours is typically under 5 minutes on a single-state CDL driver and under 15 minutes on a 3-state CDL driver. Orders placed during AAMVA maintenance windows queue and clear when the system returns; the dashboard flags the wait reason so the operator never has to guess.

Related guides