In our ELD recordkeeping post we said the device side — picking hardware that stays on the registered list — was its own subject. Here it is, and the reason it needs its own post is a fact most owner-operators never hear at the point of sale: the cheapest ELD on the market and the best one get onto FMCSA's registered list by exactly the same mechanism. Neither was tested by the government. Both vendors filled out the same form and checked the same box certifying their own device conforms to the rule.
That single fact reorganizes the whole buying decision. You are not choosing a device FMCSA vetted. You are betting on a vendor's claim about its own product — and FMCSA has spent the last eighteen months pulling devices off the list in batches when those claims didn't hold up. If you're on the wrong end of one of those removals, you have a short window to replace the device before your truck is running with no valid record of duty status at all.
This post is how to make that bet well.
How a device gets on the list: self-certification, not approval
Here's the part that surprises people. There is no FMCSA lab. There is no government testing facility that puts ELDs through their paces before they're allowed on the market.
Under the ELD rule — 49 CFR Part 395, Subpart B (§395.20 through §395.38), with the technical detail in Appendix A to that subpart — a vendor registers its device with FMCSA and certifies that the device meets the specification. FMCSA's own guidance is blunt about what that does and doesn't involve: manufacturers may use any test procedure they choose, FMCSA will not provide a third-party testing service, and the agency will only investigate devices it later suspects of non-conformance. The registered list page itself carries the disclaimer in plain text: the devices are self-certified by the manufacturer, and FMCSA does not endorse any of them.
So when §395.22(a) requires you to use only an ELD that appears on FMCSA's registered list, it is requiring you to use a device whose vendor claimed conformity — not one FMCSA confirmed. Being on the list is necessary. It is not a quality signal, and treating it as one is the first mistake.
The list has two halves — and you have to read both
What most carriers picture as "the ELD list" is actually two lists living at the same place (eld.fmcsa.dot.gov): a Registered list of devices certified and in good standing, and a Revoked list of devices FMCSA has removed.
FMCSA's guidance on this is direct and it puts the duty on you: the motor carrier is responsible for checking that its device is registered, and that means checking both the registration list and the revocation list periodically. The agency says it will make efforts to notify the public when it removes a device — but your vendor is under no obligation to tell you they've been pulled. A vendor whose product just got revoked is not highly motivated to email you the news. The carrier who checks the list is the carrier who finds out in time.
What revocation actually does to you
When FMCSA removes a device, it follows the process in Appendix A, section 5.4: written notice to the provider stating the reasons for removal and any corrective action required. Then the device moves to the Revoked list, and a clock starts for every carrier running it.
The window is 60 days. FMCSA states it the same way in every removal notice: motor carriers have up to 60 days to replace the revoked ELD with a compliant one. During those 60 days you're expected to stop using the revoked device and revert to paper logs (or compliant logging software), and enforcement is encouraged not to cite drivers for the transition.
After the 60 days, the protection ends. A driver still running the revoked device is treated as having no record of duty status at all — cited under §395.8(a)(1) — and placed out of service under the CVSA Out-of-Service Criteria. The device you paid for becomes, overnight, the same as no device.
One distinction worth nailing down, because the numbers get confused constantly: the 60-day list-removal window is not the 8-day malfunction window. Those are two different clocks for two different events. The 8-day clock (covered below) is for when your own working device breaks. The 60-day clock is for when FMCSA pulls your device's certification out from under you. Don't let a vendor or a forum post tell you that you have 8 days to deal with a revocation, and don't assume you have 60 to deal with a malfunction.
This is not hypothetical — the purge is aggressive and ongoing
The reason this post exists rather than a generic "buy a good ELD" listicle is that FMCSA has been removing devices at a pace that makes "is my device still valid?" a live question, not a theoretical one.
As of FMCSA's May 20, 2026 removal notice, the agency reported that it had removed 79 devices since January 2025 for failing to meet federal standards — and that figure climbs with each new batch, so treat it as a floor, not a fixed number. The removals come in clusters. A sample from FMCSA's own published notices in just the last several months:
- December 8, 2025 — PSS ELD, Black Bear ELD, and RT ELD Plus, among others (replace-by February 7, 2026).
- February 12, 2026 — a batch of nine devices including GTS ELD and UTRUCKIN (out-of-service exposure from April 14, 2026).
- March 4, 2026 — fourteen devices in a single notice.
- April 2, 2026 — HERO ELD (replace-by June 2, 2026).
- May 7 and May 20, 2026 — further removals, including widely-listed consumer-grade logging apps.
That's not a list to memorize — those specific names will be stale the day a new batch drops. It's a pattern to internalize: devices get pulled, regularly, in groups, and the ones that get pulled skew heavily toward the cheap, thinly-supported, app-first end of the market. FMCSA's administrator framed the program's posture in the May 2026 release in one line — safety is not optional, and neither is compliance. The agency is not slowing down.
So how do you choose one that survives?
We don't rank devices here, and we won't tell you to buy a specific brand — that's not what an honest compliance resource does, and the list changes too fast for a recommendation to stay good. But the self-certification reality points to a small set of durability questions that actually matter, and they're not the ones the sales page emphasizes.
Is it on the Registered list right now, and absent from the Revoked list? This is the floor, not the ceiling, but check it yourself at eld.fmcsa.dot.gov before you pay — don't take the vendor's word, and don't take a reseller's. Search both lists.
How long has the vendor been registered, and how established are they? A device that's been on the list for years from a company with a real corporate footprint is a different bet than an app that appeared eighteen months ago. Self-certification means the list can't filter for vendor durability — so you have to.
Is there a real, reachable support operation behind it? When your device malfunctions at a scale house at 11 p.m., the difference between a vendor with US-based support and a vendor that's an app store listing with a contact form is the difference between a fixed problem and an out-of-service order. This is the same durability logic that applies to any vendor holding your regulated data: the cheapest option is cheapest partly because the support and the longevity aren't there.
What happens to your data if the vendor disappears? This is the question almost nobody asks before buying and everybody asks after a revocation. If your six months of records live only in the vendor's cloud portal, and the vendor is the entity that just got pulled, "the data was in their system" is not a position you want to be in during an audit. Which is the cleanest argument for the habit in the next section.
Price, notably, is not on this list. Self-certification means price tells you nothing about compliance. A $15-a-month app and a premium hardware unit reached the registered list through the identical process. The expensive one is not certified harder.
The malfunction fallback — why the cheap device costs more when it breaks
A durable device matters because the regulation assumes your device will sometimes fail, and it puts the burden of the failure on you. §395.34 lays out the sequence when an ELD malfunctions:
- The driver notes the malfunction and provides written notice to the carrier within 24 hours.
- The driver reconstructs the current day plus the prior 7 days on paper graph-grid logs (unless that data is retrievable) and runs paper logs until the device is fixed.
- The carrier repairs or replaces the device within 8 days of discovery or notification — and if you need longer, the extension request goes to your FMCSA Division Administrator within 5 days.
This is where a flimsy device quietly costs you. A unit with a loose harness connection or a flaky cellular link doesn't just annoy you — it drops you into the §395.34 paper-log process every time it drops out, and the 8-day repair clock runs whether the vendor answers the phone or not. The cheap device's real price shows up here, in the days you spend reconstructing logs by hand because the support line is a contact form.
And this is exactly why §395.22(h) requires every ELD-equipped truck to carry an onboard information packet: the user's manual, the data-transfer instruction sheet, the malfunction instruction sheet, and blank paper RODS grids sufficient for at least 8 days. Those blank grids are not bureaucratic decoration. They're the fallback you live on the day the device fails — or the day it gets revoked. (One item in flux worth flagging under our "honest precision" standard: FMCSA published a proposal in 2025 that would rescind the in-cab operator's manual portion of this packet. As of this writing it's a proposal, not a finalized rule — so keep the full packet, including the manual, until that changes.)
What's coming — labeled clearly as not-yet-law
There's movement on the certification regime itself, and it's worth knowing the status precisely rather than the rumor.
In December 2025, FMCSA announced an overhaul of how it vets ELDs before they reach the registered list — an internal review workflow with fraud detection and tiered application outcomes, intended to block non-compliant devices before listing rather than chasing them afterward. Read that for what it is: an administrative process change inside FMCSA, not a new rule, and not a third-party testing mandate. Vendors still self-certify. The front-door screening is getting tighter; the fundamental self-certification model is unchanged.
Separately, there's a longer-running rulemaking — the "ELD Revisions" effort (RIN 2126-AC50), seeded by a 2022 advance notice that asked, among other things, whether FMCSA should adopt a real certification process. As of June 19, 2026, no proposed rule has been published on it; an internal target of spring 2026 has come and gone without a Federal Register document. If a genuine third-party certification regime ever arrives, it would come through this rulemaking — and we'll cover it when there's an actual published rule to read, not a target date to speculate about.
The takeaway for a purchase you're making today: don't buy on the assumption that a tougher certification regime is about to make the list trustworthy. It isn't here, and the self-certification reality is the one you're buying under.
Where Roadworthy HQ fits
Roadworthy HQ is not an ELD, and we won't pretend to pick or run your device — that decision, and the registered-list check, stay with you. What we handle is the half of this that survives a device change: the records.
Your monthly ELD back-up exports live in Roadworthy HQ under the same §395.22(i) six-month retention as the rest of your hours-of-service file, alongside the supporting documents matched to driver and date — so when you swap a revoked device for a compliant one, your six months of history doesn't live and die in a dead vendor's portal. The audit binder then assembles the records-plus-supporting-documents package in the structure an auditor asks for, regardless of which device produced the underlying logs. The point is durability: the device you run can change — by your choice or FMCSA's — without your record going dark.
If you'd rather track it yourself, the discipline is the same with or without us: check both FMCSA lists monthly, keep a back-up export you control, keep the blank grids in the cab, and weigh the vendor's longevity as heavily as the device's feature list. The regulation doesn't require software. It requires that your records exist, are yours, and survive the day your device doesn't.
This article is general guidance, not legal advice. 49 CFR Part 395 and FMCSA's published ELD materials are the authoritative sources, and the rules and figures described are current as of June 2026 — including the device-removal counts and the pending rulemakings, which move; FMCSA's registered and revoked ELD lists at eld.fmcsa.dot.gov are the live record, and the one to check before you buy.