Sep 2, 2026
.webp)
Every guide to a failed ELD tells you the same thing: the carrier has eight days to repair or replace it. That number is correct, and it is also why carriers get caught. Sitting in the same regulation is a second, shorter deadline that determines whether you can get more time when eight days is not enough, and it closes three days earlier. A fleet that spends the first week troubleshooting, escalating to the provider, and waiting on replacement eld hardware before concluding the repair will not land on time has already missed it.
That is the whole problem with how this rule gets summarized. The eight-day figure is the one everyone repeats. The five-day figure is the one that actually requires you to act.
Under 49 CFR 395.34(d)(1), a motor carrier must correct, repair, replace, or service a malfunctioning ELD within eight days of discovering the condition or of the driver's notification, whichever occurs first. That is the repair clock, and it is the one most carriers plan around.
Under 395.34(d)(2), a carrier seeking more time must notify the FMCSA Division Administrator for the state of its principal place of business within five days after the driver notifies the carrier under 395.34(a)(1). That is the extension clock, and it is separate.
The two clocks are not just different lengths, they are triggered by different events. The repair clock starts at discovery or driver notification, whichever comes first, which means it can begin running before any driver has said anything if your monitoring catches the fault first. The extension clock starts specifically at driver notification. In a fleet where the back office spots a device fault before the driver reports it, the repair deadline can already be several days along by the time the driver's written notice arrives and the extension window opens.
The practical consequence is that the decision about whether to request an extension cannot wait until you know the repair has failed. It has to be made while you are still trying, on incomplete information, roughly at the point where a reasonable person would still expect the fix to work.
For the underlying mechanics of what actually counts as a malfunction, including where the technical threshold sits between a data diagnostic event and a compliance malfunction, the analysis of why ELD problems do their worst damage overnight covers that ground in detail. This article picks up at the point where the malfunction is confirmed and the clocks are running.
Three obligations land on the driver immediately, and all three feed the carrier's position later.
The driver must note the malfunction and provide written notice to the carrier within 24 hours under 395.34(a)(1). Written is the operative word. A phone call to dispatch does not satisfy this, and the written notice is the document that starts your extension clock and proves when it started.
The driver must then reconstruct the record of duty status for the current 24-hour period and the previous seven consecutive days on graph-grid paper logs meeting 395.8, unless the driver already holds those records or they remain retrievable from the ELD. This is more work than most drivers expect, and it is the step most often done badly under time pressure. From that point forward the driver keeps manual records until the device is serviced and back in compliance.
The driver also needs to keep a copy of that written notification in the cab. If the truck is inspected while the device is down, 395.34(b) requires the driver to hand the officer the manually kept records, and the notification is what establishes that the malfunction was reported rather than discovered by the officer. What an officer actually does with a failed device at the roadside is covered separately in the ELD roadside inspection guide.
For a fleet, the useful thing to build here is not a policy document. It is a template. A pre-written malfunction notice a driver can fill in from the cab in two minutes produces a cleaner record than whatever gets improvised at a truck stop at 11pm, and it timestamps the start of both clocks in a form you can produce later.
The request goes to the FMCSA Division Administrator for the state of the carrier's principal place of business. J.J. Keller's compliance guidance also points to a dedicated submission address at ELD-Extension@dot.gov, which is worth confirming against your own division office before relying on it.
Under 395.34(d)(2), the request must be signed by the motor carrier and must contain four things: the name, address, and telephone number of the carrier representative filing it; the make, model, and serial number of each affected ELD; the date and location of each malfunction as reported; and a concise statement describing the good-faith efforts already made to repair, replace, or service the units, including why more than eight days is needed.
That fourth element is the one that decides the outcome. Under 395.34(d)(3), FMCSA may allow additional time if it determines the carrier is continuing to make a good-faith effort. The agency is not evaluating whether your device broke, it is evaluating whether you are genuinely working the problem. A request that documents specific dates, specific contacts with the provider, a replacement unit on order with a ship date, and a concrete reason the eight days will not be enough reads very differently from one that asserts more time is needed.
This is also where an operational habit pays off in a way most fleets never anticipate. If your support escalations are documented with dates and reference numbers as a matter of routine, the good-faith statement writes itself from records you already have. If they are not, you are reconstructing a timeline from memory under a deadline.
Here is the part of 395.34 that carriers most consistently miss, and it is the reason the five-day deadline matters rather than being a technicality.
Under 395.34(d)(5), a carrier that has filed a request meeting the requirements of (d)(2) is deemed in compliance with 395.8(a)(1)(i) and (a)(2) until FMCSA makes its determination, provided the carrier and driver continue to meet the other requirements of the section. You are not waiting in violation while the agency reviews. You are covered from the moment a properly formed request is on file.
That protection is exactly what a carrier facing a supply delay, a discontinued device, or an unresponsive provider needs, and it is available only to carriers who filed inside the five-day window. Miss the window and there is no mechanism to claim it retroactively.
FMCSA responds in writing under 395.34(d)(4), the determination may carry conditions the agency considers necessary for hours-of-service compliance, and it constitutes final agency action.
For fleets that would rather have someone check the paperwork before it goes out than discover a defect in it later, the eld support team is available around the clock and has seen how these requests are typically structured.
If the eight days lapse with no repair and no approved extension, the position changes materially. FMCSA guidance is direct: a driver recording hours on paper beyond eight days after the malfunction, without proof of an extension, may be placed out of service.
The mechanism is worth understanding, because it is not a paperwork citation. Once the permitted paper-log period ends, the driver is treated as having no record of duty status under 395.8(a)(1), which is the same posture as running with no ELD at all. That triggers the out-of-service criteria, and the truck stops where it is.
The cost of that outcome is almost never the fine. It is the load that does not deliver, the driver stranded away from home, the CSA entry that persists in the scoring window, and the insurance conversation that follows. The full accounting of what a single serious ELD violation actually costs is laid out in the guide to ELD violations and fines.
Set against that, the extension request is a signed one-page document filed inside five days. The asymmetry is not close.
There is a version of this that is genuinely a one-off. Hardware fails, the provider ships a replacement, the fleet is back inside a week and the extension process is never needed.
There is another version where a carrier finds itself filing extension requests more than once, or discovering the same fault pattern across multiple trucks, or waiting on a provider whose support response has stretched from hours to days. At that point the malfunction procedure is treating a symptom. A device that fails repeatedly, or a provider that cannot supply replacement units on a workable timeline, is a procurement problem wearing a compliance costume.
The signal worth watching is not the failure itself but the response time behind it. Every ELD has some failure rate. What separates providers is whether a replacement is in the mail the same day or whether you are still explaining the problem to a second-line agent on day six with your extension window closing. If you have reached the point of building process around your provider's failures, the guide to switching ELD providers without a compliance gap covers how to move without creating a second problem in the transition.
If you want to see how a platform handles device faults, replacement logistics, and support escalation before you are testing it against a live deadline, start a free 14-day trial of AI ELD and put the support side under real conditions rather than evaluating it from a feature list.
eCFR. "49 CFR 395.34: ELD Malfunctions and Data Diagnostic Events." Primary regulatory source for the entire procedure covered in this article: the driver's 24-hour written notice requirement and RODS reconstruction obligation under (a), the inspection requirement under (b), the eight-day repair window under (d)(1), the five-day extension filing deadline and required request contents under (d)(2), the good-faith determination standard under (d)(3), the written determination and final agency action language under (d)(4), and the deemed-compliance protection under (d)(5).https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395/subpart-B/section-395.34
FMCSA ELD Program. "ELD Malfunctions and Data Diagnostic Events, Frequently Asked Questions." Primary source confirming that the extension request goes to the FMCSA Division Administrator for the state of the carrier's principal place of business, must be filed within five days of driver notification, and must be signed by the carrier, along with the requirement that drivers maintain paper records of duty status where the malfunction prevents accurate recording.https://eld.fmcsa.dot.gov/FAQ/Topics?name=ELD_Malfunctions_and_Data_Diagnostic_Events
FMCSA. "Cross Border Transportation ELDs, Hours of Service FAQ." Primary source for the enforcement consequence: recording duty status on paper beyond eight days after a malfunction, without proof of an FMCSA extension, may result in the driver being placed out of service.https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/2020-02/FMCSA-BOR-HOS-ELD-395-FAQ004.nj_.docx
J.J. Keller Compliance Network. "Oh No, an ELD Malfunction. What You Need to Do in 5 Easy Steps." November 2025. Source for the practical submission route via ELD-Extension@dot.gov as an alternative to writing directly to the state FMCSA office, and for the operational point that the request should be filed early enough for FMCSA to act before the eight-day window closes. Note that this article cites the malfunction provisions as 395.24 while the same publisher's regulatory reference page cites 395.34, which matches the eCFR. Verify the section number against the eCFR before relying on any secondary summary.https://jjkellercompliancenetwork.com/news/oh-no-an-eld-malfunction-what-you-need-to-do-in-5-easy-steps
AI ELD. "The 3 AM Problem: Why ELD Issues Do Their Worst Damage Overnight." Source for the technical threshold separating a data diagnostic event from a compliance malfunction, and for the discovery-versus-notification trigger on the repair clock.https://ai-eld.com/insights/the-3am-problem-eld-violations-overnight
AI ELD. "ELD Roadside Inspection: What Drivers Must Know." Source for what happens at a roadside stop when the device is down, including the paper log transition and the documentation a driver needs to have in the cab.https://ai-eld.com/insights/eld-roadside-inspection-guide
AI ELD. "How to Switch ELD Providers Without a Compliance Gap." Source for the transition mechanics relevant to carriers whose malfunction pattern indicates a provider problem rather than an isolated hardware failure.https://ai-eld.com/insights/how-to-switch-eld-providers