FMCSA's MOTUS Registration System Crashes Two Weeks After Launch

The Federal Motor Carrier Safety Administration (FMCSA) shut down its Unified Registration System, Licensing and Insurance public filing system, and FMCSA Portal registration functions permanently at 8:00 PM Eastern on May 14, 2026. The agency replaced all three with MOTUS, a single centralized platform tied to Login.gov identity verification. Two weeks later, carriers trying to file authority updates, renew bonds, or access their own records are reporting system-wide failures loud enough that the rollout has become its own compliance crisis.

What is MOTUS and why did FMCSA force the switch?

MOTUS is FMCSA's new registration platform, built to consolidate carrier filings that previously lived across three separate legacy systems. The agency designed MOTUS to reduce fraud by requiring Login.gov identity verification for every user who touches a carrier record. Login.gov is a federal single-sign-on service that uses two-factor authentication and identity proofing. FMCSA retired the old systems to modernize infrastructure that had been running on code built decades ago and to tighten control over who can access operating authority records.

The cutover was not optional. After 8:00 PM Eastern on May 14, carriers could no longer file MCS-150 updates, upload insurance certificates, or register new USDOT numbers through the old portals. Every carrier, broker, freight forwarder, and process agent now must use MOTUS.

What carriers are experiencing in the first two weeks

Social media, compliance forums, and direct carrier reports describe login failures, frozen screens, lost filings, and error messages that provide no actionable troubleshooting steps. One user on X called the MOTUS rollout "one of the worst software releases I've ever witnessed." The post, published May 29, reflects frustration building across the industry as carriers hit the same problems repeatedly with no clear timeline for fixes.

Carriers report that Login.gov identity verification is rejecting valid driver's licenses and state IDs during the proofing step, blocking users from creating accounts. Others say they completed identity verification but MOTUS will not link their Login.gov account to their existing USDOT number, leaving them locked out of their own records. Filings submitted before the May 14 cutover are missing from MOTUS, forcing carriers to re-upload insurance certificates and MCS-150 data they had already filed through the legacy portals.

Process agents and third-party filing services report that MOTUS is not recognizing their authority to file on behalf of carriers, even when the carrier has granted explicit permission through the system's delegation tools. That breakdown is forcing small fleets to handle filings in-house that they previously outsourced, adding compliance workload at a time when many are already stretched thin.

Why this matters for small fleets and owner-operators

FMCSA requires carriers to update their MCS-150 data every 24 months. Missing that deadline triggers a deactivation of your USDOT number and operating authority. If MOTUS will not accept your filing or locks you out of your account, you cannot meet the deadline. A deactivated USDOT number means you cannot legally dispatch trucks until FMCSA reactivates the authority, and reactivation requires a manual review that can take weeks.

Insurance filings are equally time-sensitive. If your insurer files a cancellation notice and you do not upload proof of replacement coverage within the required window, FMCSA suspends your authority. MOTUS login failures or filing errors during that window put your operating authority at risk through no fault of your own.

New entrants trying to register a USDOT number for the first time are reporting that MOTUS is rejecting applications with generic error codes that do not explain what data field failed validation. That delays the start of the new-entrant safety monitoring period and pushes back the date when a carrier can begin hauling regulated freight.

FMCSA has not published a fix timeline or workaround guidance

As of May 30, FMCSA has not issued public guidance on how carriers should handle MCS-150 deadlines, insurance filing windows, or new-entrant registrations when MOTUS system failures prevent timely submission. The agency has not published a list of known bugs, a fix timeline, or temporary workarounds for carriers locked out of their accounts.

That silence is forcing carriers into a compliance gray zone. If you cannot file because the system is broken, are you out of compliance? If FMCSA deactivates your authority because a MOTUS bug prevented your MCS-150 update, do you have recourse? The agency has not answered those questions publicly.

Industry observers note that FMCSA ran a beta test of MOTUS before the May 14 launch, but the beta was invitation-only and limited to a small group of carriers and filing services. The problems surfacing now suggest the beta did not capture the load, user diversity, or edge cases that a full production rollout would hit.

What to do if MOTUS is blocking your filing this week

Document every login attempt, error message, and failed filing with screenshots and timestamps. If FMCSA later questions why you missed a deadline, that documentation is your evidence that the system, not your compliance process, failed.

If you are approaching an MCS-150 deadline or insurance filing window and MOTUS will not accept your submission, contact FMCSA's National Consumer Complaint Database at 1-888-DOT-SAFT (1-888-368-7238) and file a report. Reference the specific error code or behavior MOTUS displayed. Ask the representative to note in your carrier record that you attempted to file on time but the system rejected the submission. That creates a paper trail.

If you are a new entrant and MOTUS is blocking your USDOT registration, call the same number and escalate. New-entrant authority has a defined start date for the safety monitoring period, and delays caused by system failures can push your first revenue loads back by weeks.

If you use a process agent or third-party filing service, confirm with them in writing that MOTUS is the source of the filing failure, not a missing delegation or account-linking step on your end. If the problem is on FMCSA's side, you need that confirmation documented.

Check FMCSA's MOTUS support page daily for updates. The agency may publish workarounds, extended deadlines, or manual filing procedures as it works through the backlog of failures. Do not assume the problem will resolve itself before your next compliance deadline.

The compliance risk small fleets are carrying right now

FMCSA built MOTUS to reduce fraud and tighten control over operating authority records. Those are legitimate goals. But a registration system that locks carriers out of their own records, rejects valid filings, and provides no clear path to resolution creates a different kind of risk. Small fleets that cannot file MCS-150 updates, upload insurance certificates, or register new authority because the system is broken are now carrying compliance exposure they cannot control.

The longer FMCSA goes without publishing a fix timeline, workaround guidance, or deadline extensions for carriers affected by MOTUS failures, the more that exposure compounds. A carrier deactivated for missing an MCS-150 deadline because MOTUS rejected the filing is not a compliance failure on the carrier's part. It is a system failure. FMCSA needs to acknowledge that distinction publicly and provide relief for carriers caught in the gap.