Aug 26, 2026
.webp)
Almost everything written about FMCSA ELD revocations recycles the same secondary reporting: a device count, a deadline, a warning to check your device. Very little of it goes to the agency's own notices, which are public, dated, and considerably more specific than the coverage suggests. Read the primary record and a few patterns show up that nobody has flagged, including one that changes how a carrier should think about waiting out a revocation rather than replacing the device. This matters for anyone running eld fleet management across more than a truck or two, because the decision is not really about the device at all. It is about whether you are willing to bet an out-of-service order on a third party's engineering timeline.
Every revocation notice contains four identifying fields for each device: the ELD name, the model number, the ELD identifier, and the provider. It also carries the revocation date and an enforcement deadline set exactly 60 days out. That level of specificity matters because carriers frequently know their provider's brand name without knowing the model or identifier actually registered under it, and the identifier is what determines whether a specific installation is affected.
What FMCSA does not publish, anywhere, is which motor carriers use which ELD. There is no public mapping between a carrier and its device. This is why the agency notifies the industry by mass email rather than contacting affected carriers directly. It cannot contact them directly, because it does not know who they are. The practical consequence for a fleet manager is that nobody is going to tell you personally that your device was revoked. FMCSA sends a general notice to whoever is subscribed, your provider has an obvious incentive not to lead with the news, and the responsibility to check falls entirely on you.
FMCSA stated its own figure plainly in the May 20, 2026 removal announcement: since January 2025, the agency had removed 79 devices for failing to meet federal standards. That is the agency's number, from the agency's own release, not a trade estimate.
It is worth comparing that to how the number gets reported elsewhere. A compliance industry article published in June 2026, a month after FMCSA's own statement, put the figure at "56+ devices since January 2025." The agency had already said 79. Secondary reporting on this topic runs behind and undercounts, which is a reasonable argument for checking the primary notices rather than trusting a summary.
Adding the two removal actions documented after that statement, TRUCKSTAFF ELD on June 23, 2026 and ten further devices on July 9, 2026, the total stands at no fewer than 90 as of early July 2026. That figure is arithmetic on published FMCSA notices rather than an agency-stated total, so treat it as a floor rather than a precise count.
The cadence through 2026 is visible in the notices themselves. Three devices on December 8, 2025. Nine on February 12, 2026. Fourteen on March 4. A single device, HERO ELD, on April 2. Twelve on May 20. A single device, TRUCKSTAFF ELD, on June 23. Ten on July 9. The pattern is not a steady trickle. It is a series of batch actions punctuated by individual removals, which suggests the agency is working through technical reviews in groups rather than responding to complaints one at a time.
Here is the first thing the primary record shows that the coverage consistently gets wrong. Revocation counts are reported as though each device represents a failed company. They do not.
In the February 12, 2026 action, FMCSA removed nine devices. Four of those nine were AirELD, listed separately as Android with Xirgo 6300 Series, iOS with Xirgo 6300 Series, Android with PT30, and iOS with PT30, each carrying its own ELD identifier. One provider, Aireld Technologies, accounted for nearly half the action. The headline said nine devices. The reality was six providers.
This matters when you are trying to read the enforcement environment. A carrier looking at "79 devices revoked" reasonably concludes that dozens of separate companies have collapsed. The actual number of failed providers behind that figure is meaningfully smaller, because a provider supporting multiple hardware platforms or both mobile operating systems registers a separate device entry for each combination. The enforcement is real and the acceleration is real. The number of companies involved is smaller than the device count implies.
The second pattern is one I have not seen written about anywhere, and it sits in plain text inside the notices.
FMCSA's own device tables carry former names. The February 12, 2026 action lists "HOST ELD LLC (f/k/a FACTOR ELD)" and "ELD365 (f/k/a ELOG365)." The July 9, 2026 action lists "Ev ELD Inc. (f/k/a Evo ELD Inc.)." Three separate providers, documented in the agency's own records as operating under a prior name at or near the point of revocation.
There is a legitimate version of this. Companies rebrand for ordinary commercial reasons and the former name is disclosed as a matter of record-keeping. But the pattern is worth knowing about during due diligence, because a provider trading under a name with no history is harder to evaluate than one with a track record attached to it, and the agency is clearly tracking the connection even when the marketing does not.
The practical step is small. When evaluating a provider, search the former name as well as the current one, and check whether the entity has appeared on the revoked list under any name. This is the same underlying concern covered in the analysis of what happens when an ELD provider disappears, approached from the registration record rather than the business-failure angle.
Reading the model numbers across the revoked list turns up something that will reassure some carriers and should concern others. The PT30 appears repeatedly. UTRUCKIN registered its device on the PT30. Two of the four AirELD entries run on the PT30. Going back further, ELD MANDATE PLUS carried the model designation EMPPT30.
The PT30 is a widely used telematics platform that also sits behind devices that remain registered and fully compliant, including hardware in use across compliant platforms today. The same is true of other shared hardware. What this tells you is that revocation is a judgment about the provider's implementation and ongoing compliance, not a defect in the underlying hardware platform.
This distinction matters in both directions. A carrier should not assume a device is safe because the hardware is familiar and widely deployed, since the hardware is the part that varies least between providers. And a carrier should not assume a device is compromised because the same hardware platform appears somewhere on the revoked list, since the failure was in the provider's software, firmware maintenance, or compliance posture rather than the box itself. If you want to see which hardware platforms sit behind a compliant setup and how they are supported, the ELD hardware options page covers the specific devices in use.
Every FMCSA revocation notice contains the same sentence: if the provider corrects all identified deficiencies, the agency will place the device back on the registered list and inform the industry. Reinstatement is a real mechanism. Providers know it, and they say so.
There is a documented example of exactly how this gets communicated to customers. When FMCSA revoked four devices in July 2024, a member of the TFM ELD support team told a trade publication that the company was working on correcting the issues and that the device "should be reinstated back soon." That is precisely the reassurance a carrier receives when they call their provider after a revocation, and it is worth examining carefully rather than accepting at face value.
Notice what the reinstatement mechanism does not include. There is no published timeline. There is no service level commitment. There is no requirement that the provider notify you of progress or of failure. There is no partial credit for being close. FMCSA's language is conditional on the provider correcting all identified deficiencies, and the agency explicitly encourages carriers to act now rather than wait, warning in every notice that deficiencies may not be addressed at all.
[NEED: verified reinstatement outcome data. Producing an actual reinstatement rate requires cross-referencing the complete historical revoked list against the current registered list, which is not available through public reporting. One compliance industry source asserts that most revoked devices stay revoked because the underlying business or compliance problem is usually terminal, but that is a claim rather than a verified figure and is presented here as such.]
The decision does not actually require that statistic, which is the point. Set the two timelines side by side. Your enforcement deadline is fixed, published, and dated in the notice itself. Your provider's remediation timeline is unknown, uncommitted, and entirely outside your control. On day 61, an officer at a roadside inspection is not going to weigh whether your provider is close to a fix. The device is either on the registered list or it is not, and if it is not, your driver is placed out of service under the CVSA criteria for operating without a record of duty status.
Waiting for reinstatement means accepting a certain deadline in exchange for an uncertain remedy, with the downside landing on your operation rather than on the provider whose failure created the situation.
The enforcement structure inside that window is more specific than most summaries convey, and understanding it prevents both panic and complacency.
During the 60 days, safety officials are encouraged not to cite drivers using the revoked device under 395.8(a)(1) for no record of duty status, or under 395.22(a) for failing to use a registered ELD. Instead they are directed to request paper logs, logging software, or to use the device display as a backup method for reviewing hours-of-service data. Carriers are expected to discontinue the revoked device and revert to paper logs or logging software during the transition.
That grace is not permission to keep operating normally. It is a window to complete a replacement while remaining inspectable. Once the stated date arrives, the treatment changes completely: the carrier is considered to be operating without an ELD, and the driver is placed out of service. The cost structure of an out-of-service order, which extends well past the citation itself into downtime, lost revenue, and CSA impact, is covered in the analysis of ELD violations and fines.
The mechanics of executing the replacement cleanly, including historical data portability and the rolling seven-day record problem, are covered separately in the guide on how to switch ELD providers. This article is about reading the record and making the decision. That one is about carrying it out.
None of this requires waiting for a revocation to affect you. Pull the ELD identifier for your registered device, not just the brand name on the app, and confirm it currently appears on the FMCSA registered list at eld.fmcsa.dot.gov. Check the former name of your provider as well as the current one. Subscribe to FMCSA's ELD update emails directly rather than relying on your provider to tell you, since the provider is the party least motivated to deliver that news quickly.
If your device has been revoked and you are inside the 60-day window, the useful posture is to treat the deadline as real and the reinstatement as a bonus if it happens, rather than the reverse.
If you are replacing a revoked device against a deadline and want to confirm compatibility and timing before committing, the support team is available around the clock and can walk through the transition against your specific date. If you would rather evaluate the platform on your own trucks first, start a free 14-day trial and run it alongside your current setup during the window.
FMCSA. "FMCSA Removes 12 Devices from List of Registered Electronic Logging Devices." May 20, 2026. Primary source for the agency's own count of 79 devices removed since January 2025, the July 20, 2026 enforcement deadline, and Administrator Derek D. Barrs's statement on enforcement posture. https://www.fmcsa.dot.gov/newsroom/fmcsa-removes-12-devices-list-registered-electronic-logging-devices
FMCSA. "FMCSA Removes 10 Devices from List of Registered Electronic Logging Devices." July 9, 2026. Primary source for the ten-device removal action, the September 8, 2026 enforcement deadline, and the "Ev ELD Inc. (f/k/a Evo ELD Inc.)" provider naming record. https://www.fmcsa.dot.gov/newsroom/fmcsa-removes-10-devices-list-registered-electronic-logging-devices
FMCSA. "FMCSA Removes Fourteen Devices from List of Registered Electronic Logging Devices." March 4, 2026. Primary source for the fourteen-device removal action and the May 4, 2026 enforcement deadline. https://www.fmcsa.dot.gov/newsroom/fmcsa-removes-fourteen-devices-list-registered-electronic-logging-devices
FMCSA. "FMCSA Removes TRUCKSTAFF ELD from List of Registered Electronic Logging Devices." June 23, 2026. Primary source for the single-device removal and the August 23, 2026 enforcement deadline. https://www.fmcsa.dot.gov/newsroom/fmcsa-removes-truckstaff-eld-list-registered-electronic-logging-devices
FMCSA ELD Program. "Revoked ELDs, February 12, 2026 industry email." Primary source for the nine-device removal action including the four separate AirELD registrations, and the "HOST ELD LLC (f/k/a FACTOR ELD)" and "ELD365 (f/k/a ELOG365)" provider naming records. https://eld.fmcsa.dot.gov/File/OpenKey/FMCSA_Removed_9_ELDS_GOVDelivery
FMCSA ELD Program. "Revoked ELD: HERO ELD, April 2, 2026 industry email." Primary source for the April 2, 2026 single-device removal, the June 2, 2026 deadline, and the standard reinstatement language. https://eld.fmcsa.dot.gov/File/OpenKey/REVOKED_ELD_HERO_ELD_Industry_Email_April2_2026
FMCSA ELD Program. "Revoked ELDs, December 8, 2025 industry email." Primary source for the three-device removal action and the February 7, 2026 enforcement deadline. https://eld.fmcsa.dot.gov/File/OpenKey/Revoked_ELDs_December8_2025
FMCSA ELD Program. "Revoked ELDs, May 21, 2024 industry email." Primary source for the ELD MANDATE PLUS registration under model designation EMPPT30, used here as evidence of shared hardware platforms across revoked and compliant devices. https://eld.fmcsa.dot.gov/File/OpenKey/Revoked_ELDS_05-21-2024_Email
Commercial Carrier Journal. "FMCSA places four ELDs on 'Revoked Devices' list." July 2024. Source for the TFM ELD support team's statement that the company was working on corrections and expected reinstatement soon, used here as a documented example of how reinstatement expectations are communicated to carriers. https://www.ccjdigital.com/regulations/safety-compliance/article/15680167/fmcsa-places-four-elds-on-revoked-devices-list
Heavy Vehicle Inspection. "FMCSA ELD Revoked Devices List 2026." June 2026. Secondary source, cited specifically for its assertion that most revoked devices stay revoked because the underlying issue is often terminal, and as the example of secondary reporting undercounting the agency's own figure. https://heavyvehicleinspection.com/blog/post/fmcsa-eld-revoked-list-2026
eCFR. "49 CFR 395.8(a)(1) and 395.22(a)." Primary regulatory source for the violations cited when a carrier operates past the replacement deadline on a revoked device. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395