Regulatory update · FCC & rulemaking
Fake Cops, Fake Coinbase and a Swatting Call: The FCC Puts Gateway Provider RGTN on Notice
Here's the thing ... a lot of people think robocall enforcement is just about car warranty spam. Then you read a letter like this one and realize the same pipes carry way scarier stuff.
On this page
On August 24, 2026, the Federal Communications Commission (FCC) Enforcement Bureau sent a Notification of Suspected Illegal Traffic to RGTN USA Inc., a New York-based company. The FCC says RGTN was the gateway provider, meaning the U.S. entry point, for illegal calls coming from abroad.
Where the calls came from
According to the letter, RGTN received every one of these calls straight from a foreign provider, TheSwissXperts AG, which lists a business address in Switzerland. Then RGTN carried them onto the U.S. network.
What the calls were
The FCC identifies five categories of traffic: Buckle up.
- Fake IT department. On May 1, 2026, three employees of Blue-Grace Logistics LLC got calls on their personal cell phones from someone pretending to be the company's IT department, trying to get internal company emails. The caller ID showed Blue-Grace's own toll-free number. The traceback ended at a provider called GUGUcompany, which didn't respond.
- Fake police. On April 24, 2026, a call displayed the number and name of the Hawley, Texas Police Department. Spoofed.
- Fake federal agents. On January 9, 2026, a call displayed a number associated with a Virginia port of entry of U.S. Customs and Border Protection (CBP). Also spoofed.
- Fake Coinbase and Amazon. Prerecorded robocalls from January 5 to May 24, 2026 claimed to be from the "Coinbase Security Department" or "Amazon Customer Support." The Amazon version claimed you'd been charged $1,279.99 and told you to press one. Other robocalls claimed to be from Walmart.
- Swatting. Calls made false claims about bomb threats, shootings and other horrific events. One spoofed the number of the InfoAge Science and History Center in Wall, New Jersey, and led to the evacuation of about 500 conference attendees.
Read that again. Swatting calls through a gateway provider.
What the FCC says was illegal
The FCC says the spoofed calls apparently violated the Truth in Caller ID Act, and that the prerecorded robocalls apparently violated the Telephone Consumer Protection Act (TCPA). Those robocalls hit "honeypot" numbers run by ZipDX and Verizon, numbers with no real subscriber, so nobody could have consented.
What RGTN has to do
The letter provides RGTN with these deadlines:
- 48 hours to effectively mitigate the illegal traffic and tell the FCC and the Industry Traceback Group (ITG) what steps it took.
- 14 days to put measures in place to stop new and renewing customers from originating illegal calls.
- 14 days to investigate, block the identified traffic and substantially similar traffic, and report back.
If it doesn't comply, downstream providers can block all of its traffic. The FCC can order mandatory blocking. And RGTN could lose its spot in the Robocall Mitigation Database (RMD).
Why you should care
If you're a carrier or you sell voice service, "we just pass traffic through" isn't a defense. The gateway is the choke point, and the FCC knows it.
What to do
- Know your upstream. Where's the traffic really coming from?
- Answer tracebacks fast. Ignoring them is how you end up in a letter like this.
- Watch for spoofed government and brand numbers.
That's it. Know who you're carrying.
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.
