Regulatory update · FCC & rulemaking

FCC Proposes $4.5 Million Penalty Against Voxbeam Over Spoofed Bank Robocalls

The Federal Communications Commission (FCC) has proposed a $4,500,000 penalty against Voxbeam Telecommunications Inc. for apparently carrying foreign robocall traffic from a provider that was not listed in the Robocall Mitigation Database (RMD). The Notice of Apparent Liability for Forfeiture (FCC 26-22) was adopted March 31, 2026 and released April 2, 2026.

By Harrison GevirtzPublished 3 min read
On this page

The bottom line: if you accept foreign traffic that uses U.S. numbers, you must confirm the upstream provider is in the RMD first. It is a simple check, and skipping it is expensive.

What happened

The FCC said that between March 31, 2025 and April 3, 2025, Voxbeam transmitted tens of thousands of calls onto the U.S. network from Axfone, LLC, a voice service provider located in Czechia. Axfone was not listed in the RMD.

The FCC says that many of those calls appear to have spoofed the fraud prevention or customer service numbers of U.S. financial institutions, including Bank of America and Chase Bank. Caller ID spoofing means falsifying the number that appears on the recipient's phone so the call looks like it comes from someone they trust.

The FCC's Enforcement Bureau worked with the Industry Traceback Group (ITG), the industry group that traces suspected illegal robocalls back to their source. Four tracebacks on calls from April 1 and April 2, 2025 identified Voxbeam as the gateway provider carrying the traffic directly from Axfone. A gateway provider is the first U.S. provider to receive a call from a foreign provider.

According to the notice, Voxbeam said Axfone had been a customer since 2012. Voxbeam blocked Axfone on April 3, 2025, less than one day after it received the first of the four traceback requests.

The law

The Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act) directed the FCC to require caller ID authentication (STIR/SHAKEN) and robocall mitigation programs. The FCC created the RMD in 2020. Providers must file certifications and robocall mitigation plans there.

The rule at issue is 47 C.F.R. § 64.6305(g)(2). In plain terms, a U.S. provider may not accept traffic that uses U.S. numbers in the caller ID field directly from a foreign provider that is not listed in the RMD. Providers must also respond fully to traceback requests within 24 hours under 47 C.F.R. § 64.1200(n)(1).

Where the matter stands

A Notice of Apparent Liability is a proposal, not a final finding. The FCC states that Voxbeam "apparently" violated the rule. Voxbeam may respond before the FCC takes any final action. You can read the full notice here: FCC Notice of Apparent Liability against Voxbeam.

Note the timing. Prompt blocking after a traceback did not remove the exposure. The rule is about whether the upstream provider was in the RMD when the traffic was accepted.

Why it matters

The FCC cites Federal Trade Commission (FTC) data showing consumers lost $12.5 billion to fraud in 2024, and Federal Bureau of Investigation (FBI) data reporting $16.6 billion in scam and cybercrime losses that year. Bank impersonation calls are a large part of that problem.

The FCC is treating intermediate and gateway providers as gatekeepers. A long customer history does not substitute for a current RMD check.

What this means for you

  1. Check every foreign upstream provider against the RMD before you accept its traffic.
  2. Recheck on a schedule. Listings can be removed.
  3. Put RMD status and traceback cooperation in your carrier contracts.
  4. Answer traceback requests within 24 hours, and keep records of your response.
  5. Watch for traffic spoofing bank, government, or brand customer service numbers.

Know your upstream provider. Verify it in the database. Document that you did.

Not legal advice. TCPA.com provides general information, not legal advice, and is not a substitute for the advice of an attorney. Do not rely on it. Verify any action with your own licensed lawyer before you take it. See our Terms of Use.

Primary sources

  1. Notice of Apparent Liability for Forfeiture, In the Matter of Voxbeam Telecommunications Inc., FCC 26-22, File No. EB-TCD-25-000386591 (adopted Mar. 31, 2026; released Apr. 2, 2026).
Harrison Gevirtz, Chief Strategy Officer of Ringba, Las Vegas, Nevada

About the Author: Harrison Gevirtz

Harrison Gevirtz serves as the Chief Strategy Officer (CSO) of Ringba, a call tracking and pay per call platform, and is based in Las Vegas, Nevada. Harrison Gevirtz is a serial operator in call tracking, call routing and telemarketing operations, and for the past several years he has focused on how federal regulations affect the daily operations of these industries. At TCPA.com, Harrison Gevirtz covers TCPA litigation, Telemarketing Sales Rule (TSR) enforcement, tech support fraud prosecutions and Federal Communications Commission (FCC) rulemaking in a way that's accessible to the non-lawyer executive or compliance manager.

More from Harrison Gevirtz

Topics