FMCSA revokes 10 ELDs: what carriers must do before September 8, 2026

On July 9, 2026, FMCSA pulled ten Electronic Logging Devices off the registered list — Ontime Logs, Last Minute ELD, Porter ELD, Zee HOS, Ev ELD (formerly Evo), Light and Travel ELD, PremierRide Logs, two 2BRO devices, and TT ELD 40. Motor carriers have 60 days to switch to a compliant device. After September 8, drivers still using them get placed out-of-service under 395.8(a)(1).

The short version

On July 9, 2026, FMCSA officially removed 10 Electronic Logging Devices from the registered ELD list. Every carrier currently running one of these boxes has 60 days, until September 8, 2026, to replace it. After that date, drivers still using the revoked devices will be treated as if they have no ELD at all and placed out-of-service on the spot under 395.8(a)(1), per Commercial Vehicle Safety Alliance OOS criteria.

FMCSA Administrator Derek D. Barrs, in the bulletin: "We will continue to take decisive enforcement action to ensure that only compliant, reliable devices are used on our nation's roadways." Read literally, that's a promise: this is not going to be the last revocation list of the year.

The full list of revoked devices

These are the ten devices removed today. The Est. users column is our own market estimate of how many drivers each provider had before the revocation — based on carrier-fleet chatter, provider marketing, and the fact that several of these devices are clones or whitelabels of the same base platform. Treat the numbers as directional, not audited.

ELD Provider	Device	Model	ELD ID	Est. users	Notes
ONTIME LOGS INC	Ontime Logs iosix	OTL101	24b11f	n/a	reported clone of TT ELD
Last Minute ELD	LAST MINUTE ELD	360-LM	LMN932	~2,000	reported clone of Zee HOS-247
Porter ELD	Porter ELD	Porter 1	POR247	n/a	—
Zee App	Zee HOS Compliance	TTELD101	F594EF	n/a	same TTELD101 firmware family
Ev ELD Inc. (f/k/a Evo ELD Inc.)	EV ELD IOSIX (f/k/a EVO ELD IOSIX)	EV 2 (f/k/a EVO 2)	G711H3	~10,000	reported whitelabel of TT ELD
LIGHT AND TRAVEL LLC	Light and Travel ELD	LNTRA	LNT780	~2,000	—
PREMIERRIDE LOGS LLC	PREMIERRIDE LOGS	1RIDE	PRD391	~1,000	—
TWO BRO SECURITY & IT SOLUTIONS	2BRO ELD	2BRO002	2BRELD	20,000+	combined 2BRO + 305 ELD user base
TWO BRO SECURITY & IT SOLUTIONS	305 ELD	305002	2BR305	20,000+	same vendor as 2BRO ELD
TT ELD Inc	TT ELD 40	PT40	TTAH49	30,000–50,000+	base platform for several clones on this list

Source: FMCSA public bulletin, July 9, 2026 (device / model / ID columns). Devices were revoked for failing to meet the minimum requirements set in 49 CFR Appendix A to Subpart B of Part 395. User counts are Carrierintel estimates from public market signals and are not confirmed by the providers.

Add the numbers up and it points to a very uncomfortable ceiling: on the order of 65,000–95,000+ drivers could be running a device that stops being legal on September 8. A large share of that exposure is concentrated in a single family — TT ELD and its reported clones/whitelabels (Ev/Evo, Ontime Logs, Zee HOS) — which is exactly the concentration-risk pattern we warned about below.

What carriers have to do — the exact timeline

Right now: stop using the revoked ELD. Fall back to paper logs or compliant logging software to record hours of service until the replacement device is installed.

Before September 8, 2026: replace the revoked device with a compliant one from the FMCSA Registered Devices list. This is a hardware and integration project, not a checkbox — start now, not the last week of August.

Until September 8, 2026: inspectors are instructed not to cite drivers for 395.8(a)(1) ("no record of duty status") or 395.22(a) ("failing to use a registered ELD") if the driver is using a revoked device — as long as the driver can produce paper logs, logging software, or the ELD display as a back-up. That grace period ends in 60 days.

On and after September 8, 2026: any driver still using a revoked device gets cited under 395.8(a)(1) and placed out-of-service. The truck stops moving until compliance is restored. That's not a fine; that's parked equipment and a missed load.

If a revoked provider fixes the deficiencies, FMCSA will restore the device to the list and notify the industry. But the bulletin is clear: don't wait for that to happen. Assume the deadline sticks and switch now.

Why this is happening on this schedule

This revocation is not an isolated event. It's the third public step in a much larger enforcement wave FMCSA has been rolling out in 2026:

Step 1 (April 1, 2026): activation of violation code 395.8(e)(2) — a surgical tool for citing ELD tampering at the roadside.

Step 2 (April–June 2026): that code lit up the data. In our tampering surge report we tracked 3,715 violations across 1,893 inspections and 1,579 carriers in just over two months, with Arizona alone running a 98% Out-of-Service rate. The message from the roadside was that a non-trivial share of ELDs in the field are being manipulated — sometimes by drivers, sometimes by dispatch, and sometimes by the device itself.

Step 3 (today, July 9, 2026): FMCSA pulls the devices at the source. If a provider can't meet the minimum spec — anti-tampering controls, event integrity, authentication, engine synchronization — the device is off the list and every carrier using it has to move.

Steps 1 and 3 reinforce each other. When inspectors have a clean tampering code and a shrinking pool of "compliant" devices to compare against, the enforcement surface widens quickly. It's much harder for a marginal ELD vendor to hide when the revocation list keeps growing and every citation ties back to a specific device signature.

What we think comes next

Based on the shape of the data we're seeing on our live tampering dashboard , this is the pattern to expect for the rest of 2026:

More revocations, in bigger batches. FMCSA has publicly committed to "decisive enforcement action." The registered-ELD list has hundreds of entries and a long tail of small vendors with minimal engineering staff. Expect another batch inside the next quarter.

Concentration risk for small fleets. Many of the revoked devices are favored by 1–5-truck carriers because they're cheap. A single revocation event can knock hundreds of small fleets offline for a week or more if they don't have a replacement lined up.

Tampering citations will keep climbing. Every carrier scrambling to swap hardware in the next 60 days is a carrier whose logs, drivers, and dispatch workflows are in transition — exactly the conditions under which 395.8(e)(2) violations get written. Inspectors know the deadline too.

Broker and insurer due diligence will start pulling ELD signals. Once the revoked-device list becomes a moving target, "which ELD does this carrier use?" becomes a question every serious counterparty asks before booking a load or binding coverage. We're already seeing early requests for that data through our API.

Bottom line

If you run trucks, do three things this week: check which ELD is installed in every unit, confirm none of the ten revoked devices are in your fleet, and if any are, contact your replacement vendor today — not on Labor Day. If you broker or insure carriers, add a revoked-ELD check to your vetting flow. The regulatory environment for hours-of-service compliance in the US is tightening on a visible curve, and September 8 is the next hard checkpoint on that curve.

The §395.8(e)(2) tampering surge — full report

Why Arizona is running a 98% OOS rate on ELD tampering inspections, and what the data says about where the next wave lands.

Read the tampering report