FCC Warns Gateway Provider RGTN USA Over Alleged Illegal Robocall and Spoofing Traffic

Case Snapshot

• Agency: Federal Communications Commission, Enforcement Bureau
• Matter: RGTN USA Inc., Notification of Suspected Illegal Traffic
• Decision Date: Aug. 24, 2026
• Core Issue: Allegedly illegal foreign-originated calls entering the U.S. telecommunications network through a gateway provider
• Key Allegation: RGTN carried spoofed, fraudulent, and prerecorded traffic received from TheSwissXperts AG
• Agency Finding: The FCC identified traffic that apparently violated the Truth in Caller ID Act and TCPA
• Outcome: RGTN was ordered to investigate and mitigate the traffic and faces potential network blocking and Robocall Mitigation Database removal for noncompliance
• Notable Detail: The traffic included calls impersonating a private company, police, CBP, Coinbase, and major retailers, as well as a swatting call that prompted the evacuation of approximately 500 people

The FCC has warned RGTN USA Inc. that it could face network-wide blocking after the agency traced multiple allegedly illegal calls entering the United States through the telecommunications provider, including spoofed calls, fraudulent robocalls and calls impersonating businesses and law enforcement agencies.

In an Aug. 24 Notification of Suspected Illegal Traffic, the FCC Enforcement Bureau said RGTN served as the U.S. gateway provider for traffic received from Swiss telecommunications provider TheSwissXperts AG. The calls allegedly included schemes impersonating a logistics company, a police department, U.S. Customs and Border Protection, Coinbase, Amazon and Walmart, along with swatting calls reporting false emergencies.

The notice is significant for companies operating outbound calling programs because it illustrates how the FCC’s robocall enforcement framework reaches beyond the party that actually places an unlawful call. Providers responsible for carrying traffic into the U.S. network can face escalating obligations and potentially lose their ability to have calls accepted by other carriers.

FCC Traces Calls Through Foreign Providers

The FCC investigation began with a complaint from Blue-Grace Logistics LLC involving three calls made to employees on May 1. According to the agency, the caller spoofed a toll-free number assigned to Blue-Grace, impersonated the company’s information technology department, and attempted to persuade employees to search for and forward internal emails.

Blue-Grace’s provider, TeleVoIPs LLC, determined that the calls had not originated on its network.

The FCC then worked with the Industry Traceback Group to follow the calls upstream. The tracebacks ended at GUGUcompany, which the FCC said did not respond to ITG correspondence. According to the agency’s findings, GUGU sent the calls to TheSwissXperts, which then sent them to RGTN for entry onto the U.S. network.

The investigation uncovered other traffic following the same pathway.

The FCC said RGTN carried a call displaying the telephone number and caller name of the Hawley, Texas, Police Department, although the department did not make the call. Another displayed a number used by a CBP port of entry in Virginia.

Investigators also identified artificial or prerecorded calls that allegedly impersonated Coinbase and retailers including Amazon and Walmart. The FCC said recordings included messages claiming that suspicious account changes or purchases had occurred and directing recipients to respond.

FCC Points to TCPA and Caller ID Violations

The Enforcement Bureau said the traffic apparently implicated two federal statutes particularly relevant to telecommunications compliance.

The agency said the spoofed calls apparently violated the Truth in Caller ID Act, which prohibits knowingly transmitting misleading or inaccurate caller identification information with an intent to defraud, cause harm, or wrongfully obtain something of value.

Separately, the FCC said certain artificial or prerecorded calls apparently violated the Telephone Consumer Protection Act.

The robocalls were received by “honeypot” telephone numbers operated by ZipDX and Verizon, according to the notice. Because those numbers were not assigned to end-user customers, the FCC said there was no customer who could have provided consent to receive the calls. Seven calls went to numbers assigned to cellular service, while three went to numbers for which the called party incurred charges.

The FCC’s letter characterizes the underlying calls and statutory violations as “apparent” and does not constitute a final determination that RGTN violated federal law.

Swatting Call Prompted Evacuation

Among the more serious allegations was a spoofed emergency call connected to the InfoAge Science and History Center in Wall, New Jersey.

According to the FCC, the call resulted in approximately 500 conference attendees being evacuated while law enforcement searched the facility. Police ultimately determined the report was a swatting incident, a tactic involving false emergency reports intended to trigger a police response.

The Industry Traceback Group again identified RGTN as the gateway provider, with TheSwissXperts immediately upstream.

RGTN Faces Blocking and Robocall Database Consequences

The FCC directed RGTN to investigate the identified traffic and take several specific actions.

Under the agency’s rules, RGTN was told to effectively mitigate illegal traffic within 48 hours and implement measures within 14 days to prevent new and renewing customers from using its network to originate illegal calls. It also must investigate the calls identified by the FCC, block or stop accepting identified and substantially similar traffic when required, and report its findings to the Enforcement Bureau.

Failure to provide an adequate response could trigger progressively more serious measures.

The Enforcement Bureau may issue an initial determination that RGTN is not complying with FCC rules. After additional proceedings, the agency could issue a final determination directing downstream providers to block and stop accepting all RGTN traffic.

RGTN also faces possible removal from the FCC’s Robocall Mitigation Database. If that occurs, intermediate and terminating voice service providers would be required to stop accepting traffic directly from the company.

RGTN certified in February that it would cooperate with FCC investigations and efforts to stop illegal robocallers using its services. The FCC said failure to respond to the notice could be evidence that the certification is deficient.

What the Notice Means for Receivables Calling Programs

The enforcement action does not involve allegations that a debt collector generated the calls identified by the FCC. It nevertheless has implications for receivables organizations that rely heavily on voice communications.

The notice demonstrates the increasingly interconnected compliance environment surrounding outbound calling. Originators, intermediate providers, gateway providers, and terminating carriers can each play a role in whether traffic ultimately reaches consumers.

For ARM companies, carrier relationships and call authentication practices can therefore affect operational reliability even when the company itself is attempting to make lawful calls. Enforcement against an upstream or intermediate provider could potentially result in traffic being blocked downstream.

The FCC’s action also reinforces the importance of monitoring calling vendors, maintaining accurate caller identification information, and understanding how calls travel through telecommunications networks. The agency’s ability to combine Industry Traceback Group data with its blocking and Robocall Mitigation Database authorities gives it several mechanisms for removing suspected illegal traffic from U.S. networks.