Voxbeam faces $4.5M FCC forfeiture for RMD violations
Summary
The FCC's Enforcement Bureau issued a Notice of Apparent Liability (NAL) proposing a $4.5 million forfeiture against Voxbeam Telecommunications Inc. for violating Robocall Mitigation Database (RMD) requirements. The company transmitted calls from a provider that was not listed in the RMD, violating federal robocall rules under the TRACED Act.
What changed
The FCC Enforcement Bureau released NAL FCC-26-22 proposing a $4.5 million forfeiture against Voxbeam Telecommunications Inc. for apparent violations of the Robocall Mitigation Database rules. The investigation found that Voxbeam transmitted calls from a provider that was not listed in the RMD, which is required under 47 U.S.C. ยง 227(e) and associated FCC rules implementing the TRACED Act. This represents one of the largest proposed forfeitures for robocall-related violations.
Telecommunications providers must immediately audit their connections to other providers and verify that all upstream and downstream carriers are properly registered in the Robocall Mitigation Database. Any provider found transmitting calls from unregistered entities may face substantial forfeiture penalties. Voxbeam has 30 days from issuance to pay the forfeiture or contest the NAL through written arguments.
What to do next
- Audit all carrier connections to ensure upstream/downstream providers are registered in the Robocall Mitigation Database
- Update compliance procedures to verify RMD status before transmitting calls
- Review interconnection agreements for robocall mitigation compliance requirements
Penalties
$4.5 million forfeiture proposed for Robocall Mitigation Database violations
Source document (simplified)
- Full Title: In the Matter of Voxbeam Telecommunications Inc.
- Document Type: NAL
- Bureau(s): Enforcement
- Description FCC EB proposes $4.5 million forfeiture against a provider that transmitted calls from a provider that is not listed in the Robocall Mitigation Database.
- DA/FCC #: FCC-26-22
Files
Document Dates
- Released On:
Apr 2, 2026
- Adopted Date:
Mar 31, 2026
- Issued On:
Apr 2, 2026
- Tags: Enforcement Robocall Robocalls
Named provisions
Related changes
Source
Classification
Who this affects
Taxonomy
Browse Categories
Get Telecom & Technology alerts
Weekly digest. AI-summarized, no noise.
Free. Unsubscribe anytime.
Get alerts for this source
We'll email you when FCC Headlines publishes new changes.