Revoked ELD List Compliance Guide (2026)

The FMCSA revoked ELD list is the official record of Electronic Logging Devices removed from the agency's Registered Devices list because the devices or their providers failed to meet minimum requirements under 49 CFR Appendix A to Subpart B of Part 395. Fleets can check the list at the official FMCSA ELD portal (eld.fmcsa.dot.gov), which displays both the Registered Devices list and the Revoked Devices list side by side. Every device carries three identifiers you can verify: ELD Name, Model Number, and unique ELD Identifier. Your device appears on exactly one list. Since January 2025, FMCSA has removed 79+ devices from the Registered Devices list, with the pace of removals accelerating through 2026 — recent batches include 9 devices in April 2026, 14 devices across two May 2026 actions (Safe ELD/MYLOGS plus a separate 12-device batch), and 10 additional devices in June 2026. Every fleet should check the revoked list at least monthly, and immediately whenever FMCSA issues an industry-wide email notification of new removals. The list is the only authoritative source — do not act on unverified secondary reports.

FMCSA gives motor carriers exactly 60 days from the revocation date to replace a decertified ELD with a compliant device from the Registered Devices list. This is the actual regulatory window — not the "30-day" figure that occasionally circulates in industry chatter, which is incorrect. During the 60-day replacement window, FMCSA instructs safety officials at roadside inspections not to cite drivers using the revoked device for 395.8(a)(1) "No record of duty status" or 395.22(a) "Failing to use a registered ELD." Instead, drivers should be prepared to present paper logs, logging software output, or use the ELD display as a backup method for hours-of-service review. FMCSA explicitly instructs carriers using revoked devices to either revert to paper logs or use logging software during this window. Beginning the day after the 60-day deadline, carriers who continue operating on the revoked device will be considered as operating without an ELD — a serious violation that triggers out-of-service placement under Commercial Vehicle Safety Alliance criteria. The clock is calendar-strict: a device revoked on January 13 must be replaced by March 15; a device revoked on May 20 must be replaced by July 20. There is no built-in extension mechanism.

The consequences at roadside inspection depend entirely on whether the 60-day replacement window has expired. Before the deadline, safety officials are instructed not to issue ELD-specific citations for the revoked device. Drivers should present paper logs, logging software output, or the ELD display as backup for hours-of-service review. Documented interim compliance during this window generally avoids escalation. After the deadline, the situation changes dramatically. Safety officials will cite the driver under 49 CFR 395.8(a)(1) "No record of duty status" and place the driver out-of-service in accordance with CVSA Out-of-Service Criteria. Out-of-service means the driver cannot legally operate the vehicle until the compliance issue is resolved — typically requiring a compliant ELD replacement, restoration of hours-of-service data, and confirmation of the correction. The OOS citation itself feeds into the carrier's CSA BASIC scores, specifically Hours-of-Service Compliance, and appears on the carrier's public safety profile visible to shippers, brokers, and insurance underwriters. For carriers operating with Amazon Relay or other tight-compliance freight networks, an OOS citation can trigger cascading load-access consequences. The financial exposure includes the citation itself, the operational cost of the stopped truck, missed delivery penalties, and downstream CSA and insurance impact. Prevention through proactive vendor monitoring is dramatically cheaper.

The most effective risk-reduction strategy is proactive vendor evaluation combined with vendor-independent compliance record-keeping. On vendor selection: assess ELD providers using a tiered risk framework. Tier 1 providers have 100,000+ vehicle fleet bases, established compliance teams, 24/7 support with published SLAs, and clean or immediately-corrected revocation histories. Tier 2 providers are viable but require quarterly monitoring and self-cert audit trail confirmation at contract renewal. Tier 3 providers — small fleet base, deep discount pricing, minimal support — carry elevated revocation risk and require active contingency planning. On warning signs, monitor for: deteriorating support responsiveness, firmware updates slowing or stopping, stale company website and documentation, aggressive discount pricing that undercuts established providers, and absence from CVSA and industry conference engagement. Three or more warning signs simultaneously should trigger vendor evaluation. On documentation architecture: keep compliance records (DVIRs, PM history, work orders, driver qualification files, inspection responses) on a platform independent from your ELD. When FMCSA revokes a device, the ELD data migrates but the surrounding operational evidence stays. Fleets whose compliance records live inside the ELD lose institutional history during vendor migration. Fleets whose records live independently keep the full audit trail across any number of ELD changes.

HVI addresses ELD revocation risk from the operational-records side rather than the ELD-vendor side, which is what makes the platform vendor-independent. HVI holds every DVIR (with photo evidence and signed audit trail), preventive maintenance record, work order, inspection response, driver qualification file, cost line per unit, and safety flag on one platform — separate from whichever ELD you're currently running. When FMCSA revokes a device and you enter the 60-day replacement window, the operational and compliance evidence that underpins your CSA BASIC scores, insurance underwriting readiness, Amazon Relay compliance, and FMCSA audit position doesn't move with the ELD change. It stays exactly where it is, ready for export or audit review at any moment. This architecture matters because carriers who consolidate too much compliance history inside a single ELD platform face a difficult migration problem: the historical data either has to be exported (often in formats that don't preserve context), reconstructed manually, or accepted as lost. Fleets running HVI alongside any registered ELD get the operational continuity that makes vendor migration a routine 60-day project rather than a scramble. Published customer data shows fleets on HVI report approximately 25% lower annual maintenance cost and typical payback around 3 months — and the vendor-independence value shows up most clearly when regulatory events force a change on someone else's timeline.