FMCSA Revokes 10 More ELDs, Three Came From Repeat Offenders

Which ELD manufacturers lost devices for the second time?

FMCSA revoked ten electronic logging devices on July 9, 2026, for failing the minimum technical requirements in 49 CFR Appendix A to Subpart B of Part 395. Three of the ten came from manufacturers the agency had already sanctioned once. OnTime Logs Inc. lost its second device in eight months. Ev ELD Inc. (formerly Evo ELD Inc.) lost its second device in nine months after rebranding. Two Bro Security & IT Solutions lost two devices simultaneously. All ten are on the revoked list as of this afternoon.

The ten devices are: OnTime Logs iOSix from OnTime Logs Inc., LAST MINUTE ELD from Last Minute ELD, Porter ELD from Porter ELD, Zee HOS Compliance from Zee App, EV ELD IOSIX from Ev ELD Inc., Light and Travel ELD from LIGHT AND TRAVEL LLC, PREMIERRIDE LOGS from PREMIERRIDE LOGS LLC, 2BRO ELD and 305 ELD from TWO BRO SECURITY & IT SOLUTIONS, and TT ELD 40 from TT ELD Inc.

Add today's ten to the twelve from May 20, the single device from June 23, and the total since January 2025 is ninety. That is 4.9 devices per month, the same pace calculated seven weeks ago. The enforcement tempo has not changed.

What is the compliance deadline for carriers using these devices?

Carriers running any of the ten devices must stop using them now. Revert to paper logs or compliant logging software. Replace the device with a compliant ELD from the registered list before September 8, 2026. Before that date, roadside enforcement officers will not cite drivers using the revoked devices for 49 CFR 395.8(a)(1) or 395.22(a). Officers will ask for paper logs instead.

On and after September 8, drivers will be cited for no record of duty status and will go out of service under the Commercial Vehicle Safety Alliance (CVSA) criteria. The truck stops. The load does not move. The violation lands in the Safety Measurement System (SMS) and in every carrier vetting system that pulls FMCSA data, and it stays there.

Why did three manufacturers lose devices twice?

OnTime Logs Inc. is on today's list. FMCSA already revoked an OnTime Logs device on November 20, 2025. That one was called Ontime Logs PT, model number OTL100. The one pulled today is called Ontime Logs iosix, model number OTL101. One digit apart. Eight months apart. Same company, both devices gone.

Ev ELD Inc. is on today's list. The bulletin says Ev ELD Inc. (f/k/a Evo ELD Inc.). Formerly known as. The device is EV ELD IOSIX, f/k/a EVO ELD IOSIX. The model is EV 2, f/k/a EVO 2. FMCSA revoked EVO ELD 1 on October 17, 2025. That device carried ELD identifier G711H2. The device revoked today carries the identifier G711H3. Sequential. Consecutive. Registered back-to-back by the same company, revoked nine months apart, with a rebrand in between. Evo became Ev. They dropped a letter.

Two Bro Security & IT Solutions lost two devices, 2BRO ELD and 305 ELD, in the same announcement. Not sequentially. Simultaneously. Whatever engineering problem existed in one existed in both. Two SKUs, one codebase. This is an IT security firm selling hours-of-service compliance hardware to motor carriers.

What did FMCSA Administrator Barrs say about the revocations?

Administrator Derek Barrs put carriers on notice: "We will continue to take decisive enforcement action to ensure that only compliant, reliable devices are used on our nation's roadways. Accurate hours-of-service records are essential to protecting public safety, supporting fair enforcement, and ensuring accountability across the commercial motor vehicle industry."

Note the word that was not in the May statement. Accountability. The agency is signaling that it is tracking repeat offenders, even when they rebrand.

Does the FMCSA registry show which manufacturers have lost devices before?

No. The structural problem is that when the agency revokes a device, it revokes a device. It does not revoke a provider. There is no debarment. There is no waiting period. There is no bar on a company whose ELD was pulled for failing the technical spec from filling out a fresh self-certification form the next morning, under the same LLC or a new one, and receiving a fresh ELD identifier for a device running the same firmware that just failed.

Nothing in the ELD rule prevented any of that. FMCSA appears to have caught the Evo-to-Ev rebrand, which is why the f/k/a is in the bulletin at all. That is a sign the agency is paying attention in a way it was not two years ago.

But the registry has no vendor-level record. Nothing in it links a provider's revoked device to that provider's still-registered devices. Nothing in it links a company to its own prior name. Nothing in it links fourteen brands to the one holding company that owns them all. Carriers vetting an ELD purchase cannot query "has this company ever had a device revoked" and get an answer, because the list is organized by device, not by the entity behind it.

What should carriers check before buying an ELD?

If your ELD is still on the registered list, do not assume you are safe. Check when the device was registered. Check whether the manufacturer answers the phone. Check whether they have shipped a software update in the last twelve months. Now, check the harder thing: whether the company selling you that device is the same company it was a year ago, and whether the name on your invoice has ever appeared on a revoked-device bulletin under a different spelling.

Check whether any of the manufacturer's other devices have been revoked, because a manufacturer that loses one device to a compliance failure may have the same engineering problems across its entire product line. Today's bulletin is that sentence with a case number attached.

Two of today's devices carry "iosix" in the name. IOSiX is a Michigan-based hardware maker whose vehicle dongle is white-labeled by ELD sellers that do not build hardware. In April 2024, the Cybersecurity and Infrastructure Security Agency (CISA) published an advisory on the iOSix IO-1020 Micro ELD covering vulnerabilities, including a default WiFi password and a flaw, scored 9.6 out of 10, that let the device download and run code without checking where it came from. IOSiX shipped a fix. The point is not that today's iOS-badged devices carry that flaw. The point is that when the same physical box sits behind a dozen brand names, a defect in the box is a defect in all of them, and the registry has no way to show you that. The list of ten providers is not ten engineering teams.

What happens if a manufacturer fixes the deficiency?

If the provider corrects all identified deficiencies, FMCSA puts the device back on the registered list. Devices should be fixable. The question is: who verifies the fix? The rule that put the device on the list in the first place was self-certification. Is the fix self-certified too? If a provider tells the FMCSA that it has corrected the deficiency, what does the agency verify before the device is returned?

That question matters more when the same manufacturer has lost two devices. If the first device failed for a technical deficiency, and the second device from the same company failed nine months later, what assurance does a carrier have that a third device from that company will pass?

What compliance action should fleets take this week?

If you are running any of the ten devices named in the July 9 bulletin, stop using them today. Switch to paper logs or a compliant ELD from Carrier Atlas's electronic logging device review before September 8. After that date, roadside enforcement will cite you for no record of duty status and place your truck out of service.

If you are running an ELD that is still on the registered list, verify that your manufacturer has not had another device revoked. Check the FMCSA registered device list weekly. Check whether your manufacturer has shipped a software update in the last twelve months. If the company has gone silent, or if the name on your invoice does not match the name on the registered device list, start shopping for a replacement now. Do not wait for the revocation bulletin.