On August 6, 2026, FMCSA removed five electronic logging devices from its registered list because they failed to meet minimum federal requirements. Carriers using those devices had exactly 60 days to replace them. That deadline – October 6, 2026 – has passed. If your fleet was affected and you haven’t acted, you may already be operating in violation.

But this article is about more than five devices. It’s about a pattern that catches motor carriers off guard repeatedly: the assumption that buying compliance technology is the same thing as being compliant. It isn’t.

Compliance technology still requires compliance management. That’s the lesson every safety department should take from the October 6 deadline.

Key Takeaways

• Owning an electronic logging device does not automatically make your fleet ELD compliant. FMCSA can – and does – remove ELD devices from its registered list when they fail to meet the ELD rule’s technical specifications.
• After October 6, 2026, continued use of five specific revoked ELD devices is treated the same as operating without an ELD. Drivers operating commercial motor vehicles with these devices can be cited and placed out of service.
• The motor carrier – not the ELD provider, not the driver – is responsible for periodically checking both the FMCSA registered and revoked ELD lists to verify that its devices remain compliant.
• ELD compliance extends well beyond device registration. It includes managing ELD data, hours of service violations, ELD malfunctions, driver training, record retention, and data integrity across the operation.
• Compliance technology (ELD systems, ELD solutions, fleet management software) still requires active compliance management by the safety department. Software assists compliance. It does not run your safety program.

---

Having an ELD Does Not Automatically Mean You Are Compliant

Many fleets operate under a simple and dangerous assumption: “We bought an ELD, therefore we are compliant.”

Here is what that assumption looks like in practice. A motor carrier purchases an ELD system in 2022. They install ELD devices in every tractor. They train commercial motor vehicle drivers on how to use it. They integrate it with dispatch. The device works. Drivers log their hours. Everything runs smoothly for years.

Then in 2026, a driver gets stopped at a roadside inspection. The inspector checks the device against FMCSA’s list. The ELD is no longer registered. The driver is cited. The truck is parked.

How did a “compliant” fleet become non-compliant without changing anything?

Because the ELD mandate, which started on December 18, 2017, doesn’t just require you to install a device. It requires use of a registered device – one that appears on the FMCSA-maintained public list of registered ELD devices. As of early 2026, over 900 ELDs are registered on that list. But registration is based on manufacturer self-certification. ELDs must be tested and certified by an accredited laboratory and must meet technical specs in 49 CFR §395.20–§395.38. FMCSA can later determine that a device no longer meets those standards and revoke its registration.

ELDs automatically track driving time and duty status changes. They provide precise and automated tracking of driver hours. They help enforce federal hours-of-service regulations. And 97% of CMV drivers must use ELDs – that includes drivers operating vehicles over 10,000 pounds and interstate CMV drivers generally required to maintain records of duty status.

But compliance involves more than having hardware in the cab. The motor carrier must ensure:

• ELD data is accurate and complete
• Hours of service limits are managed
• Supporting documents are retained
• ELD malfunctions are handled according to proper procedures
• ELD records can be transferred during roadside inspections

An ELD solution is a tool. The carrier still owns the compliance program – the policies, the driver coaching, the internal audits, and the responses to ELD violations that make the whole system work under 49 CFR Part 395.

---

What Happened With the October 6, 2026 ELD Deadline?

Here’s what happened, in plain English.

On August 6, 2026, FMCSA announced that five electronic logging devices ELDs were being removed from the registered ELD list because their providers failed to meet the minimum technical specifications required under 49 CFR Part 395, Appendix A. ELDs must meet specific technical standards set by FMCSA, and these five did not.

The five affected devices were:

1. MOONLIGHT ELD
2. HGRS ELD
3. HIGHEST ELD
4. TRUCKFORD ELD
5. Sparkle ELD

These revocations apply to specific ELD systems – not necessarily to every product that a company may sell in every market.

FMCSA’s instructions to carriers using any of these devices were straightforward:

• Stop using the revoked device as your compliant ELD immediately
• Switch to paper logs or compliant logging software following ELD malfunction procedures during the transition
• Install a replacement registered ELD that appears on the current FMCSA ELD list by October 6, 2026

FMCSA maintains a public list of registered ELD devices. The agency also explicitly allows providers to correct deficiencies and request that a device be returned to the registered list.

Important: Before relying on any named device’s status in this article, verify the current registration status against FMCSA’s live Registered and Revoked ELD lists. A device listed as revoked at the time of writing may have been reinstated if the provider corrected the deficiencies.

This wasn’t the only batch of revocations in 2026. In March, fourteen devices were revoked – many associated with Gorilla Fleet Safety. In May, Safe ELD and MYLOGS ELD were removed. The pattern is clear: FMCSA is actively reviewing and enforcing the ELD rule applies requirements, and carriers need to keep up.

---

What Happens After an ELD Replacement Deadline Passes?

October 6, 2026 was not a soft suggestion. It was a hard compliance deadline.

FMCSA’s August 6 announcement stated that once the replacement deadline expires, any driver still using one of the revoked devices would be considered to be operating without a compliant electronic logging device. That driver can be cited under 49 CFR 395.8(a)(1) – the “no record of duty status” violation – and treated exactly as if no ELD existed in the vehicle at all.

At a roadside inspection, the consequences are immediate:

• Inspectors issue ELD violations
• The driver may be placed out of service under CVSA criteria
• The driver may be required to switch to paper logs before the commercial motor vehicle can continue
• Electronic logs facilitate faster roadside inspections, but only when the device is compliant – a revoked device creates delays, not efficiency
• ELDs simplify the process of regulatory compliance and inspections, but only when they’re registered

The operational impact hits fast and hard:

Impact Area	What Happens
Driver	Cited, placed out of service, delayed
Truck	Parked at scale or weigh station
Load	Interrupted, potentially missed delivery
Dispatch	Scrambling to reassign or recover freight
Customer	Late delivery, damaged relationship
CSA Score	Hours-of-Service Compliance BASIC affected
Safety Department	Incident to investigate and document

What appears to be an IT or vendor issue – a revoked ELD device – instantly becomes a safety, operations, and customer service problem. A truck parked at a scale doesn’t care whose fault it is. The load is still late.

---

Who Is Responsible for Making Sure an ELD Is Still Registered?

FMCSA puts this responsibility squarely on the motor carrier. Not the ELD provider. Not the driver. The carrier.

FMCSA guidance states that carriers must ensure the electronic logging devices they use appear on the registered ELD list and must periodically review both the registration and revoked ELD lists for changes affecting their devices. The ELD rule applies to drivers maintaining a record of duty status, and it’s the carrier’s job to make sure the technology supporting those records is legitimate.

Here are assumptions that carriers commonly make – and each one is risky:

• “Our ELD provider will tell us if the device gets revoked.” FMCSA does not require vendors to notify every customer of a removal. Some do. Some don’t.
• “Our drivers would notice if something was wrong.” Drivers are focused on driving. They are not monitoring FMCSA announcements.
• “The device was compliant when we bought it, so it must still be compliant.” Self-certification is not permanent. FMCSA can revoke at any time.
• “FMCSA tested and approved our device.” FMCSA does not “endorse” or continuously re-test every registered ELD. Registration is self-certification by the provider.

Each motor carrier should treat ELD verification as an internal compliance responsibility. Think of it the same way you think about monitoring driver qualification files, drug testing programs, and vehicle maintenance records. None of those are things you check once and forget. ELD registration is no different.

---

ELD Verification Should Be Part of Your Compliance Calendar

The safest way to avoid being caught by a future revocation is to build ELD verification into your recurring compliance routines – not to wait for an emergency or an FMCSA press release.

There is no federal regulation that mandates an exact frequency for checking the FMCSA ELD list. But companies should establish a recurring internal review schedule appropriate for their operation. Quarterly checks, or reviews aligned with existing safety meetings, are reasonable starting points.

Here’s what a verification review should include:

1. Confirm the exact ELD provider name, ELD solution name, model number, and ELD identifier currently in use across the fleet
2. Cross-check those details against FMCSA’s current registered-device list
3. Review FMCSA’s revoked-device list for any matches
4. Document the date, findings, and person performing the review
5. File the documentation where it’s accessible during a DOT audit

Safety or compliance managers should also subscribe to FMCSA email updates and notifications. FMCSA posts announcements when ELD devices are added, removed, or when new ELD rule guidance and ELD mandate interpretations are issued. Catching a change early gives you time to plan – not scramble.

Finally, every carrier should develop a written contingency plan. If your ELD is revoked tomorrow, what happens?

• Who notifies drivers?
• Who communicates with dispatch?
• Do drivers know how to complete paper records of duty status?
• How quickly can you source and install a replacement?
• Who is authorized to approve emergency purchases?

If you don’t have answers to these questions documented, you don’t have a contingency plan. You have a hope that nothing will go wrong.

---

Do You Actually Know Which ELD Your Drivers Are Using?

If someone walked into your safety office right now and asked you for the following information, could you provide it without making a phone call?

• ELD provider
• Device name
• Model number
• ELD identifier
• Current FMCSA registration status

If the answer is no, you’re not alone. But you are exposed.

Every carrier should maintain a detailed internal ELD inventory. At minimum, this should list:

Field	Example
ELD Provider	[Provider Name]
Device/Solution Name	[Device Name]
Model Number	[Model #]
Firmware Version	[Version]
ELD Identifier	[Identifier]
Assigned Unit(s)	Tractor 101, 102, 103
Terminal/Location	Chicago terminal

This inventory becomes critical for fleets with complexity. That includes fleets with:

• Multiple terminals
• Recent acquisitions or mergers
• Leased vehicles
• Owner operators using their own ELD devices
• Multiple ELD systems across business units
• Recent vendor changes
• Decentralized fleet management

Without an accurate inventory, compliance staff can’t respond quickly when FMCSA updates the revoked ELD list. They won’t know which units are affected, how many drivers need to switch to paper logs, or which terminals to prioritize.

Link this ELD inventory to your driver and equipment lists. That way, safety managers and authorized safety officials can quickly answer audit questions like: which drivers used which ELD record during a specific date range, or which tractors were drivers operating under which device at a given terminal.

---

An ELD Vendor Is Not Your Compliance Department

ELD providers deliver technology and services. They do not transfer the motor carrier’s regulatory responsibility to themselves. The legal obligation for DOT compliance – including hours of service and ELD rule compliance – stays with the carrier.

Here are misconceptions that surface repeatedly:

• “The ELD system will automatically prevent all HOS violations.” It won’t. ELDs reduce the risk of errors and false reporting, but they don’t physically stop a truck. Dispatch can still assign loads that push drivers past legal limits.
• “The vendor configured the system for our exact operations.” Maybe at installation. But did they configure personal conveyance rules, yard move policies, and ELD exemptions correctly for your specific operation? Did they update those configurations when your operation changed?
• “The ELD provider will manage unassigned driving and unidentified driving for us.” They won’t. That’s your compliance process.
• “The system won’t let our drivers violate hours of service.” It will record the violation. It will not prevent the driver from turning the key.
• “Our ELD provider would tell us if anything was wrong with the device’s registration.” As discussed, FMCSA expects carriers to check the lists themselves.

An ELD provider cannot write or enforce your internal policies on topics like personal conveyance for local drivers, agricultural operations exemptions, short haul drivers exceptions, or how to handle ELD malfunctions during a cross-country trip. These are decisions each carrier must make and document.

Over-reliance on a vendor backfires when the vendor’s product creates a problem the carrier didn’t anticipate – or when the vendor’s registration status changes and nobody on the carrier’s side notices.

View ELD vendors as technology partners. Retain in-house ownership of compliance management, internal audits, driver training, and response to ELD violations and roadside inspection findings.

---

ELD Compliance Is Bigger Than Device Registration

The October 6 deadline illustrates the importance of verifying that your registered device stays registered. But long-term ELD compliance extends far beyond simply appearing on the FMCSA ELD list.

Safety managers need to monitor these operational areas in their ELD data:

• Recurring HOS violations captured in ELD records
• Patterns of unidentified or unassigned driving time
• Frequency and nature of driver or carrier edits to driver logs
• Use – and potential misuse – of personal conveyance and yard move statuses
• Blank driver’s records that suggest logging gaps
• Driver’s duty status accuracy across all vehicle motion and engine hours

Carriers also need clear procedures around ELD malfunctions and data transfer requirements. During roadside inspections, standardized data transfers allow ELD records to be sent instantly to authorized safety officials – but only if the driver knows how to initiate the transfer. If connectivity is limited, drivers need backup procedures. And when an ELD malfunctions, drivers must keep paper logs if the ELD malfunctions for up to 8 days while the carrier corrects the issue, following the requirements under 49 CFR 395.34.

ELDs reduce administrative costs by minimizing manual errors and paperwork. But the supporting-document expectations remain substantial. Carriers must:

• Retain ELD data and backup data for at least six months
• Protect driver privacy
• Ensure records of duty status align with supporting documents (fuel receipts, bills of lading, toll records, vehicle miles traveled)
• Produce ELD records during audits and maintain an ELD information packet onboard and an instruction sheet describing proper ELD use

A compliant device does not automatically create compliant records. Safety managers still have to interpret ELD data, investigate anomalies, and coach drivers and dispatch to prevent repeat problems. The device records driving hours. The safety program manages what those records reveal.

---

Your ELD Data Should Generate Questions, Not Just Reports

An effective safety department doesn’t simply collect and file ELD reports. It uses ELD data proactively – to identify trends, ask questions, and correct underlying issues before they become DOT findings.

The ELD mandate aims to improve safety and prevent fatigue-related accidents. Fleet managers can monitor driver fatigue levels in real-time with ELDs. Fleet managers can access real-time data on driver activities. ELDs promote road safety by monitoring driver behavior. But all of that capability is wasted if nobody acts on what the data shows.

Here are questions safety managers should be asking when reviewing HOS data and ELD records:

• Why does this driver repeatedly run out of hours near the end of every week?
• Why does unidentified driving time keep increasing at one specific terminal?
• Are certain dispatchers consistently assigning loads that cannot be delivered within legal driving time windows?
• Are drivers misunderstanding personal conveyance rules and using the status to extend their available hours?
• Why are some regions showing higher ELD violation rates than others?
• Are supervisors actually reviewing daily logs and driver logs, or just signing off?
• Are ELD violations being documented and coached – or just corrected in the system and forgotten?

ELD data should be part of a broader compliance monitoring system that includes regular driver coaching, supervisor training, and documented corrective actions for repeat violations. ELDs provide accurate records – but accuracy without action is just a well-documented problem.

Your ELD collects the data. Your safety program has to manage what that data is telling you.

---

Treat ELD Problems as a System Problem

Repeated ELD issues – whether they involve revoked devices, frequent ELD malfunctions, or high violation counts – are usually symptoms of broader system weaknesses. They are not isolated one-off mistakes by individual drivers.

Here are concrete examples, along with what they may actually signal:

Observed Problem	Possible System Issue
High volume of unidentified driving	Poor driver login procedures or vehicle assignment process
Repeated data transfer failures at inspections	Inadequate driver training on how to transfer data using wireless web services or other methods
Frequent HOS violations on ELD records	Unrealistic load scheduling by dispatch, insufficient supervision, or lack of break planning
Drivers unable to produce ELD records roadside	Missing or incomplete ELD information packet, no instruction sheet describing transfer procedures
Company discovers its ELD was revoked weeks ago	No formal process for monitoring FMCSA’s registered and revoked ELD lists

That last example brings the article full circle. Discovering – weeks after a deadline – that your device was revoked is not a communication lapse from the vendor. It’s a structural gap in your compliance management process. Nobody was watching.

When you find patterns, don’t just correct individual ELD records. Investigate the root cause. Update policies and training. Adjust processes across departments – safety, operations, HR, IT – so that improvements are durable, not one-time fixes.

Carriers that take this approach use historical data from ELD records to drive systemic improvement. They track engine power status patterns, engine control module data, and vehicle’s engine connection quality alongside record of duty status accuracy to build a complete compliance picture.

The goal is to make your fleet management system smarter over time – enabling fleet managers to prevent problems rather than react to them.

---

What Safety Managers Should Do Now

This is a practical checklist. Start here.

1. Verify your current ELD. Confirm the exact ELD provider, device/model name, and ELD identifier in use. Do not rely on “I think we use [brand name].” Confirm the specific device – not merely the company providing it. Check it against FMCSA’s current registered-device list and revoked ELD list. Document what you find.

2. Establish a recurring review process. Put ELD list verification on your compliance calendar. Revisit FMCSA’s lists regularly. Review internal HOS data for patterns of violations, ELD malfunctions, or unusual trends. Confirm that ELD exemptions – such as short haul drivers or certain agricultural operations – are applied correctly and consistently.

3. Document every verification. Record the date, who performed the check, which devices were reviewed, and what was found. During a DOT audit or compliance review, the carrier needs to demonstrate active oversight of its ELD systems – not just a purchase receipt from four years ago.

4. Subscribe to FMCSA updates. FMCSA publishes notices when devices are added to or removed from its lists. These notifications give you lead time. Use it.

5. Review your HOS management process. Don’t stop at device registration. Review what your company does with the information the ELD produces. Are supervisors reviewing driver logs? Are ELD violations being documented and coached? Are dispatch practices creating systemic HOS problems?

6. Develop or refine a contingency plan. Your safety and operations teams should know exactly what happens if FMCSA removes your ELD from the registered list. That plan should include:

• Instructions for immediate reversion to paper logs
• Internal notification procedures
• Communication templates for drivers operating in the field
• A timeline for sourcing and installing a compliant replacement
• Identification of who internally owns ELD compliance decisions

If you can’t describe this process today, build it before the next revocation catches you off guard.

---

What This Recent ELD Action Should Teach Motor Carriers

The August 6, 2026 revocations and October 6 deadline are important. But the bigger lesson is not about five specific devices. The bigger lesson is about how motor carriers manage compliance technology in general.

The core takeaway: any piece of compliance technology you purchased yesterday can create a compliance problem tomorrow if no one is responsible for monitoring whether it still meets FMCSA ELD requirements and appears on the registered-device list.

ELD rule compliance is an ongoing process. It is not a one-time project that was completed when hardware was installed. It requires continuous oversight of:

• Devices (are they still registered?)
• Data (is it accurate and complete?)
• Driver behavior (are commercial drivers following HOS rules?)
• Operations (is dispatch planning loads that can be delivered legally?)
• Records (do ELD records match supporting documents?)

Compliance technology still requires compliance management. FMCSA expects carriers to actively manage their safety programs, not simply outsource responsibility to software vendors or assume that a registered ELD guarantees perfect driver safety.

Many fleets benefit from additional expert support reviewing their ELD records, HOS processes, and broader motor carrier compliance systems. That kind of outside review can identify gaps before those gaps surface during roadside inspections or audits. The carriers that treat compliance as a managed process – not a purchased product – are the ones that hold up under scrutiny.

---

Compliance Technology Still Requires Compliance Management

An ELD can make compliance management easier. It cannot assume the motor carrier’s responsibility.

FMCSA expects motor carriers to verify that their ELD devices remain on the registered list. Carriers must understand and apply ELD exemptions correctly – whether for short haul drivers, driveaway-towaway operations, vehicles manufactured before model year 2000, or other qualifying scenarios. They must follow ELD malfunction procedures. They must ensure the accuracy and completeness of their ELD records and supporting documents, including maintaining records for logging hours accurately and retaining paper records where required.

The October 6, 2026 deadline is a practical reminder that “install it and forget it” is not an acceptable approach to ELD compliance. Carriers must build verification, driver training, internal audits, and corrective actions into their ongoing compliance calendars.

Treat ELD data as a strategic compliance asset. Use it to improve safety culture, reduce HOS violations, and strengthen readiness for DOT audits and roadside inspections – not simply as a way to avoid ELD violations after the fact. ELDs provide accurate, real-time records. The question is whether your operation is doing anything meaningful with what those records reveal.

If you’re not sure what your ELD data is saying about your operation – or whether your current HOS processes would stand up to outside scrutiny – it may be time to have someone review the program alongside your safety team and help identify the gaps before they become roadside or audit problems. Your ELD collects the data. Your safety program has to manage what that data is telling you.

---

FAQ

How often should a motor carrier check the FMCSA registered and revoked ELD lists?

FMCSA does not mandate a specific frequency. However, carriers should adopt a recurring review schedule that aligns with their risk profile. For many operations, quarterly checks – or checks tied to existing safety committee meetings, policy reviews, or internal audits – provide a reasonable starting point.

Higher-risk or rapidly growing fleets may benefit from more frequent reviews, particularly if they operate multiple ELD systems, serve drivers in interstate commerce across many states, or have a history of ELD-related violations or ELD malfunctions. Carriers transporting hazardous materials or more than eight passengers may face heightened regulatory scrutiny and should consider more frequent verification.

Document each review – the date, who performed it, which devices were checked, and what was found. This documentation demonstrates proactive oversight during DOT audits or federal motor carrier safety administration compliance reviews.

What should a carrier do if it discovers it has been using a revoked ELD after the deadline?

Stop using the revoked device immediately. Switch affected drivers to paper logs or compliant logging software as permitted under 49 CFR 395.34 while you arrange a replacement ELD from the FMCSA registered list. Drivers must keep paper logs if an ELD malfunctions for up to 8 days – the same timeline generally applies during revocation-related transitions.

Conduct an internal review to determine how long the revoked device was in use, which drivers and vehicles were affected, and whether any roadside inspections or violations occurred during the period of non-compliance.

Document all corrective actions taken. Update your policies, training materials, and ELD verification procedures. If necessary, consult with legal or compliance professionals to prepare for potential questions in a DOT audit. The carrier safety administration FMCSA will want to see evidence that you identified the problem, acted on it, and built a process to prevent recurrence.

Does using paper logs during ELD malfunctions or revocation protect a carrier from violations?

Paper logs are allowed only as a temporary measure – typically up to 8 days, unless FMCSA grants an extension – whether the need arises from an ELD malfunction or a revocation-related transition. This applies to all commercial drivers, including local drivers who normally rely on ELD solutions.

Drivers must complete paper records of duty status accurately, recording all driving time, engine hours, and duty status changes. Those records must be kept available for roadside inspection. Failure to maintain accurate paper records can still result in HOS and recordkeeping violations – blank driver’s records or incomplete logs are not acceptable substitutes.

Carriers should treat paper-log periods as high-risk windows. Ensure drivers are properly trained on how to record driving hours on paper, that logs are reconciled against supporting documents and vehicle miles traveled, and that someone in the safety department is reviewing these records closely.

How do ELD exemptions interact with revoked devices and replacement deadlines?

ELD exemptions – such as those for short haul drivers, certain driveaway-towaway operations, vehicles manufactured before model year 2000, and some agricultural operations – remain in effect regardless of revocation events. These exemptions are governed by 49 CFR 395.1 and apply based on operational criteria, not device status.

However, carriers should be careful. A driver who normally qualifies for an ELD exception but occasionally exceeds the conditions – for example, a short haul driver who goes beyond the 150 air-mile radius – must use a compliant ELD during those trips. If the device in that vehicle happens to be revoked, the driver is non-compliant. FMCSA regulations do not excuse a driver from the ELD mandate simply because they sometimes qualify for an exemption.

Regularly review which drivers are truly exempt. Verify the basis for each exemption. Ensure that non-exempt drivers – which includes drivers maintaining a record of duty status for any reason – are not inadvertently operating on revoked or non-registered ELD systems.

Can a previously revoked ELD ever be used again if FMCSA returns it to the registered list?

Yes. FMCSA allows an ELD provider to correct identified deficiencies and request that a device be reinstated to the registered ELD list. This means a device that was revoked may later reappear as a registered device if the provider addresses the technical specifications that caused the removal.

Before reactivating any previously revoked ELD in your fleet, confirm its current status directly from FMCSA’s official lists – not from the vendor’s marketing materials. Document the date you verified the renewed registration. Confirm that all devices in your fleet are running any updated software or firmware required to meet FMCSA technical specifications, and verify that the device identifier and model match what appears on the current registered list.

Treat these situations as opportunities to review broader ELD management practices. If a device was revoked and you didn’t know, that tells you something about your monitoring process. Use the experience to strengthen vendor communication, driver training, and internal monitoring of both the registered and revoked ELD lists going forward.