Removed From the Robocall Mitigation Database? Here's What It Means.
← Back to Insights
STIR/SHAKEN

Removed From the Robocall Mitigation Database? Here's What It Means.

September 16, 2026·7 min read

The fight against robocalls has fundamentally reshaped the telecommunications landscape. At the heart of this battle lies STIR/SHAKEN and the FCC’s Robocall Mitigation Database (RMD). For voice service providers inclusion in the RMD is more than just a regulatory checkbox; it's a lifeline.
But what happens when that lifeline is cut? What are the severe consequences of being removed from the RMD, and how do you navigate back to compliance?

This isn't a theoretical exercise. Recently, the FCC removed 14 voice service providers from its Robocall Mitigation Database because they failed to comply with the FCC’s robocall rules. These service providers are now effectively banned from connecting to U.S. networks.

What is the Robocall Mitigation Database (RMD)?

To truly understand the impact of removal, we first need to clarify the RMD's purpose. The Robocall Mitigation Database (RMD) is an FCC-mandated public database where all voice service providers in the United States must submit a certification outlining their robocall mitigation efforts.

Essentially, it's a transparency and accountability tool. By filing, providers certify one of two things:

1. They have fully implemented STIR/SHAKEN across their IP networks.

2. They have implemented an approved robocall mitigation program (if not fully implemented STIR/SHAKEN or operate on non-IP networks).

The RMD is designed to help other carriers and the FCC identify which providers are doing their part to combat illegal robocalls and which might be facilitating them. It acts as a gatekeeper, influencing how calls are routed across the U.S. network. It is important to note that the RMD is a crucial component of the FCC's strategy to trace, authenticate, and ultimately reduce unwanted calls.

What Does Removal from the RMD Actually Mean for Your Business?

Removal from the RMD is a catastrophic operational event for any voice service provider. The consequences are immediate and far-reaching:

· Blocking of Outbound Traffic: This is the most immediate and severe consequence. Once a provider is removed from the RMD, other intermediate and terminating voice service providers are prohibited from accepting traffic from them, meaning your outbound calls will be blocked. Your customers won't be able to make calls, severely impacting your service delivery and business operations.

· Reputational Damage: Being listed as a non-compliant provider, and having your calls blocked, will quickly erode trust with customers, partners, and other carriers.

· Loss of Revenue: With outbound calls blocked, your ability to generate revenue from call traffic ceases. Customer churn will be immediate and substantial.

· Intense Scrutiny and Penalties: Removal from the RMD signals a severe compliance failure to the FCC. This invariably leads to heightened scrutiny, formal investigations, and potentially massive financial penalties for past non-compliance.

· Operational Chaos: Re-establishing service is not a simple flip of a switch. It requires significant effort, time, and resources to regain RMD inclusion and re-establish routing relationships.

Why Do Companies Get Removed from the RMD?

Companies face removal from the RMD for several primary reasons, often stemming from a fundamental misunderstanding or disregard for their regulatory obligations:

1. Failure to File a Certification: This is the most common and easily avoidable reason. All voice service providers, regardless of size or IP/non-IP network status, must file an RMD certification. Missing this deadline or failing to file at all is a direct route to removal.

2. Filing a Deficient or Insufficient Mitigation Plan: For providers not fully implementing STIR/SHAKEN, they must submit a robust robocall mitigation plan. If this plan is deemed inadequate by the FCC (e.g., it doesn't detail effective measures, lacks accountability, or is simply boilerplate), the provider can be removed.

3. Identification as a Source of Illegal Robocalls: If a provider is repeatedly identified by the FCC's Robocall Traceback Consortium or other industry partners as originating or facilitating a high volume of illegal robocalls, the FCC can initiate proceedings to remove them from the RMD. This is often the case for "bad actor" providers.

4. Failure to Respond to FCC Inquiries: If the FCC reaches out with questions about your mitigation efforts or call traffic, a failure to provide timely and comprehensive responses can lead to adverse action, including RMD removal.

5. Misrepresenting Compliance Status: Intentionally providing false or misleading information in your RMD certification is a serious offense that will lead to removal and potentially criminal charges.

How Can a Removed Company Get Back In?

Regaining RMD inclusion is a challenging, multi-step process that requires immediate, decisive action and often expert guidance:

1. Stop the Offending Behavior: The first and most critical step is to immediately cease any activity that led to the removal (e.g., stop originating illegal robocalls, implement the missing mitigation).

2. Submit a New (and Compliant) Certification: The provider must submit a new RMD certification that fully meets all FCC requirements. This might mean:

o Demonstrating full STIR/SHAKEN implementation if that was the deficiency.

o Submitting a thoroughly revised and demonstrably effective robocall mitigation plan if the previous one was deemed insufficient. This plan must detail concrete, enforceable steps to prevent illegal robocalls.

3. Address Any Underlying FCC Orders/Investigations: If removal was part of a broader enforcement action, the provider must fully comply with all FCC orders, pay any fines, and satisfy all conditions of any settlement.

4. Provide a Detailed Explanation and Justification: The provider will need to clearly explain to the FCC (often in a formal filing) what went wrong, what corrective actions have been taken, and why they should be reinstated. This usually involves demonstrating internal controls, training, and a commitment to ongoing compliance.

5. Work with Legal and Compliance Experts: Navigating the reinstatement process is complex. Engaging specialized telecom legal counsel and compliance experts is almost always necessary to ensure all FCC requirements are met and submissions are accurate and persuasive.

6. Patience and Persistence: Reinstatement is not guaranteed and can take significant time. During this period, the provider's outbound traffic will remain blocked, underscoring the urgency.


New Plans Proposed by the FCC in order to update RMD Removal criteria.

The FCC continues to refine and strengthen its robocall mitigation rules, signaling an ongoing commitment to enforcement. Recent proposals and discussions highlight this evolving landscape:

· Expanded Scope (Potential): There's ongoing discussion about potentially expanding the RMD requirements to encompass a wider range of entities or specific types of voice traffic that may currently fall through cracks, such as certain one-way VoIP providers not traditionally considered "voice service providers" under older definitions.

· Enhanced Due Diligence Requirements: The FCC has proposed increasing the due diligence obligations for intermediate providers to ensure they only accept traffic from RMD-listed providers and to act against suspected bad actors. This could further tighten the net on non-compliant entities.

· Increased Scrutiny of Mitigation Plans: The FCC is consistently evaluating the effectiveness of submitted mitigation plans. Future rules may demand even more detailed, measurable, and independently verifiable components in these plans, pushing providers towards more robust solutions.

· Focus on Foreign Robocalls: While the RMD primarily targets domestic providers, the FCC continually seeks ways to apply similar accountability measures to gateway providers handling international traffic, preventing foreign robocalls from reaching U.S. consumers.

· Ongoing Monitoring and Audits: The FCC has affirmed its commitment to continuous monitoring of RMD data and conducting regular audits to ensure providers are adhering to their certified mitigation practices.

These proposed and ongoing updates indicate that the regulatory environment is only becoming stricter. Providers must remain vigilant and proactive.

Don't Let RMD Removal Threaten Your Business

Removal from the Robocall Mitigation Database is one of the most severe consequences a voice service provider can face in the current regulatory climate. It effectively shuts down your outbound calling capabilities, decimates your revenue, and destroys your reputation.

Navigating the complexities of STIR/SHAKEN, RMD certifications, and ongoing robocall mitigation is not just a technical challenge—it has profound financial and operational implications. Understanding these nuances, from accurate revenue allocation to robust mitigation plan development, is paramount for survival and success.

At ZIA CPA Associates, we specialize in helping US-based telecom operators bridge the gap between complex FCC compliance and sound financial strategy. We ensure your mitigation efforts protect your network and your bottom line, keeping you out of the RMD's crosshairs.

Don't wait for a removal notice to reassess your compliance strategy. Connect with us today for a proactive review of your robocall mitigation and USF obligations.


Z

ZIA CPA Associates

CPA, Telecom Compliance Specialist

ZIA CPA Associates is a specialized CPA firm for US telecom companies.

Need Help With Your Telecom Compliance?

Our CPA team handles FCC filings, USF contributions, E911 compliance and USAC reporting for VoIP providers across the US. Book a free 30-minute compliance review.

Book a Free Compliance Review
Contact Us