News · FCC & rulemaking

Robocalls to 911 Lines and Fake Medicare Pitches: FCC Targets Aspireistic and Callsto

Here's a fun one. Imagine you run a county 911 center. Your emergency line rings. It's not an emergency. It's a robocall.

By Adam YoungPublished 4 min read
On this page

Now imagine that happens eight times in 24 hours.

That's part of what the Federal Communications Commission (FCC) laid out on October 8, 2026, when its Enforcement Bureau issued Initial Determination Orders against two voice service providers: Aspireistic Inc. (DA 26-1084) and Callsto, LLC (DA 26-1085). You can read the FCC order against Aspireistic (DA 26-1084) and the FCC order against Callsto (DA 26-1085).

So what happened?

Both companies got a Notification of Suspected Illegal Traffic from the FCC's Enforcement Bureau on June 11, 2026. The FCC said their responses weren't good enough. So now each one has 14 days to send a final response and show it complies with the rules.

If they don't, the Bureau will issue a final determination order. Then any provider immediately downstream has to block all of their traffic, starting 30 days later. The orders also tell both companies to show cause why their Robocall Mitigation Database (RMD) certifications shouldn't be pulled. Get pulled from the RMD, and other providers have to stop accepting your calls directly.

Important: these are initial findings. Both companies still get a chance to respond.

What the FCC says the calls were

Callsto. According to the order, the Industry Traceback Group (ITG) identified Callsto as the originating provider for 32 robocalls placed between January 27, 2025, and November 5, 2025, without consent.

  • Ten targeted emergency lines at two public safety answering points: an emergency ambulance line in Marion County, Kentucky, and an emergency line in White County, Georgia. The Marion County line received eight calls within a 24-hour span, from eight different numbers. The customer behind those calls was based in Mumbai, India, according to Callsto.
  • The other 22 delivered prerecorded Medicare pitches to cell phones. One script: "Medicare has released many advanced benefits such as flex and food card and now you can also get cash back of up to 270 dollars."

Aspireistic. The FCC says a customer in West Bengal, India, used Aspireistic's services to place non-emergency robocalls to emergency lines at the Page County Emergency Communications Center. Two other customers, based in Egypt and India, sent prerecorded Medicare messages, some of which told recipients they had "unclaimed reimbursements left from 2025 Medicare plans." Consumers reported getting the calls "daily."

Why the responses fell short

Callsto said it wasn't the originating provider at all, just an intermediate carrier passing traffic from upstream. But the FCC says Callsto didn't name any upstream source or hand over the routing records it cited. Its own traceback responses pointed to seven end-user customers in India as the sources. That's what an originating provider looks like.

Aspireistic responded on July 7, 2026, which the FCC says was 12 days late. It said it had terminated "all foreign clients and upstream providers associated with the identified traffic," but the FCC says it gave no evidence and named no names. And here's a detail I love: certified mail sent to the Florida address in its RMD filing came back marked "NOT KNOWN."

The paperwork issues

Both companies' RMD filings had issues, according to the FCC:

  • They certified full STIR/SHAKEN implementation, while their own mitigation plans said they hadn't implemented it on non-IP parts of their networks.
  • No description of how they know their upstream providers.
  • No mention of whether they use third-party analytics vendors.

Callsto also didn't disclose that it was named in the FCC's December 10, 2024, Show Cause Order to 2,411 providers.

And the FCC says the evidence suggests the two companies are related. Both originated calls for the same campaigns. They shared unique identifying information from October 2025 to January 2026, along with two other downstream providers, INFINITYSIP and Conveytel, LLC. Each of the four ran at least some operations from Pakistan between November 6, 2025, and January 30, 2026. And Aspireistic and Callsto filed nearly identical robocall mitigation plans. The FCC wants both to explain the relationship.

Why should you care?

Look, if you carry voice traffic, this is your warning. The FCC isn't just going after the callers. It's going after the networks that let the calls in.

And if you're a lead buyer or a call center? Your carrier's RMD status is your problem too. If your provider gets cut off, your calls stop. Overnight.

What to do about it

  • Know your customers. Verify who is dialing on your network, especially foreign accounts.
  • Answer tracebacks as if your business depends on it. Because it does.
  • Keep your RMD filing honest. STIR/SHAKEN status, upstream checks, analytics vendors, affiliates, past FCC actions. All of it.
  • Keep your address current. It's not rocket science, OK?
  • Cut off anyone robocalling emergency lines. DO NOT carry robocalls to 911 centers. Period.

Robocalls to 911 lines are about as low as it gets. Don't be the network that carries them. That's it.

Source: FCC Enforcement Bureau, Initial Determination Robocall Order Against Aspireistic Inc.

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. FCC Enforcement Bureau, Initial Determination Order and Order to Show Cause, Aspireistic Inc., DA 26-1084, EB Docket No. 22-174 (Oct. 8, 2026).
  2. FCC Enforcement Bureau, Initial Determination Order and Order to Show Cause, Callsto, LLC, DA 26-1085, EB Docket No. 22-174 (Oct. 8, 2026).
Adam Young, CEO of Ringba, Miami, Florida

About the Author: Adam Young

Adam Young is a 42-year-old entrepreneur from Miami, Florida. He is the CEO of Ringba, a call tracking and pay per call platform. Adam Young has been in telecom, call routing and performance marketing for over a decade, and is the author of The Pay Per Call Revolution. At TCPA.com, Adam Young writes about the Telephone Consumer Protection Act (TCPA), robocall enforcement, tech support fraud cases and what actions by the Department of Justice (DOJ), Federal Trade Commission (FTC) and Federal Communications Commission (FCC) mean for companies that make calls. His goal is to help companies stay compliant and keep scammers off the phone network.

More from Adam Young

Topics