On September 2, 2026, the FCC’s Enforcement Bureau removed 14 voice service providers from the Robocall Mitigation Database and ordered every carrier on U.S. networks to stop carrying their calls within two business days. Companies that didn’t fix certification problems after five separate warnings got cut off from the phone system. The order targets carriers, not the businesses that originate calls, but it changes how a legitimate caller’s traffic reaches customers, and it shows how aggressively the agency is now policing the call path.
What the Enforcement Bureau ordered on September 2
The action came in an Order captioned Robocall Mitigation Database Filers, DA 26-872 (EB Sept. 2, 2026), in File No. EB-TCD-25-00038590. The Bureau found that 14 companies had failed to cure deficient database certifications and removed them. Removing a company from the database, the order states, requires every intermediate and voice service provider “to cease accepting all calls directly from the Company.”
The blocking requirement has a deadline. The Bureau ordered that “within two business days of the release of this order all intermediate providers and voice service providers MUST CEASE ACCEPTING TRAFFIC DIRECTLY FROM THE COMPANIES LISTED IN APPENDIX A,” per the same order. Removal isn’t a timeout either. The order directs that each company “shall not refile in the Robocall Mitigation Database unless and until both the Wireline Competition Bureau and the Enforcement Bureau consent.”
The 14 companies named in Appendix A are Apps Communications, CFX Business Solutions, Conference America, Convergence Technology Solutions, CSB Technologies, Digital Division, Dixie Net Communications, HIGHCOMM, Inatech Solutions, makrodepot, Opex Communications, Reachme.com, SECURE, and Skycom Healthcare. In a statement accompanying the action, FCC Chairman Brendan Carr said, “Today’s action pushes more than a dozen providers off of U.S. networks for failing to abide by our robocall rules,” according to the FCC’s news release.
How a provider lands on the removal list
The Robocall Mitigation Database is a public registry carriers file into. The FCC set it up in 2020, as the order explains, to make each carrier’s robocall mitigation visible and to hold it to what it certifies. A voice service provider has to certify things about its network and upload a robocall mitigation plan, and a carrier that isn’t listed gets cut off: “Intermediate providers and voice service providers shall accept calls directly from a domestic voice service provider” only if that provider’s filing appears in the database, under 47 C.F.R. § 64.6305.
Part of the certification is whether the provider has implemented STIR/SHAKEN. That’s the caller ID authentication system that lets carriers verify a call really came from the number it claims, so spoofed numbers are easier to flag. The current rule also makes providers commit to answering industry traceback requests, the investigations that walk a suspected illegal robocall back up the chain to its source, within 24 hours.
These 14 didn’t get removed over a single missed box. The Bureau found the companies had been “placed on notice no fewer than five times that their RMD certifications are deficient,” according to the order, going back to a December 2024 show-cause order that reached 2,411 filers and an August 2025 order that removed 1,203 of them. A March 24, 2026 show-cause order, DA 26-282, gave 35 remaining companies a last chance to cure or explain themselves. These 14 did neither.
What changes for businesses that call and text customers
The direct effect is operational, and it lands on the caller, not just the carrier. If your company originates calls or texts through one of these 14 providers, or through an upstream carrier that relied on them, your legitimate traffic can stop reaching customers once the two-business-day clock runs. Blocked calls, failed delivery receipts, and a sudden drop in answer rates are the symptoms. Nobody serves you with anything. The calls just don’t connect.
There’s a quieter effect too. The same database records that get a carrier delisted, the STIR/SHAKEN attestation level and the traceback history, are what drive spam labeling and call blocking across the networks your calls travel through. A caller whose provider carries a thin mitigation record tends to get flagged as likely spam, and that hurts answer rates long before anyone files anything. Treat your carrier’s database status as a vendor-diligence item, not a back-office detail. The FCC has now cleared the database in waves, and more removals are a safe bet, so the carrier that’s clean today may not be next quarter.
What this order does not do
Demand letters tend to blur this point. Removal from the Robocall Mitigation Database is a regulatory action against a carrier, decided by the Enforcement Bureau under its own rules. It is not a court finding that anyone violated the Telephone Consumer Protection Act, and it does not create or expand the private right of action that drives TCPA litigation. That claim lives in the statute, which lets a person recover “$500 in damages for each such violation” and up to three times that if a court finds the conduct willful or knowing, under 47 U.S.C. § 227.
So a business whose calls got blocked because a carrier flunked its certification is not, by that fact, staring at $500-per-call exposure. The order says nothing about the lawfulness of any particular campaign, and it names no originating business as a wrongdoer. Plaintiffs’ counsel sometimes point to a provider’s removal or a spam label as if it proved the caller broke the law. It doesn’t. The two questions are separate, and conflating them is a mistake a defendant should correct early and in writing. The practical risk from this order is that your calls stop working, not that this order hands a plaintiff a case.
The overlap is still real, though. A company whose attestation and traceback records are a mess is both more likely to get its carrier delisted and more likely to look bad when a private claim or a state attorney general inquiry does arrive. Clean records cut both ways.
What to check before your calls get blocked
- Ask your voice or messaging provider, in writing, whether it is currently listed in the Robocall Mitigation Database and at what STIR/SHAKEN attestation level, and get the answer in your file.
- Map the chain: find out which upstream and intermediate carriers your provider hands your traffic to, since a removal anywhere in that chain can reach you.
- Pull your recent delivery and answer-rate data so a sudden drop points you to the cause instead of a guess.
- Put database status, STIR/SHAKEN attestation, and traceback cooperation into your carrier and platform contracts as representations you can enforce.
- Talk to a lawyer before you treat a blocked-calls problem as a legal claim against you, or before you respond to anyone who says a carrier’s removal proves your calls were unlawful.
The firm’s TCPA litigation defense page covers how robocall and call-blocking disputes move through FCC enforcement and private litigation.
If a TCPA claim points to call blocking or an RMD removal
If your company is defending a TCPA claim and the other side treats a carrier’s Robocall Mitigation Database removal or a spam label as proof you ignored the robocall rules, the record usually tells a more complicated story. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving robocall and call-blocking compliance. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
The action is the Enforcement Bureau’s Order, Robocall Mitigation Database Filers, DA 26-872 (EB Sept. 2, 2026), and the FCC’s news release of the same date. The database rule is 47 C.F.R. § 64.6305, and the statute is the Telephone Consumer Protection Act at 47 U.S.C. § 227.
This post is general information about the Telephone Consumer Protection Act and related laws as of September 5, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.