RMD Annual Recertification: What U.S. Voice Providers Must Do to Stay Compliant

Why RMD Annual Recertification Is a Hard Deadline You Cannot Miss

The Robocall Mitigation Database (RMD) is not a one-time registration. Every voice service provider listed in the database — whether you filed under full STIR/SHAKEN implementation, partial implementation, or a robocall mitigation program — must complete RMD annual recertification to confirm that your compliance posture is still accurate and current.

The FCC established the RMD under the TRACED Act framework and has made clear through successive enforcement actions that outdated, inaccurate, or lapsed filings carry real consequences. As of mid-2026, the Commission is actively escalating upstream responsibility for robocall mitigation, meaning gateway providers and intermediate carriers face direct liability for traffic they accept from providers whose RMD status is deficient.

If your recertification lapses, downstream carriers are not just permitted to block your traffic — they may be required to. That is a business-ending event for a wholesale carrier or SIP trunk provider.

What the RMD Annual Recertification Requires

Recertification is not simply clicking a button. The FCC expects providers to affirmatively review and update their filing to reflect their current operational status. At minimum, your recertification must accurately represent:

• STIR/SHAKEN implementation status — full, partial, or exempt, with the correct reason code if you are not fully signed
• Robocall mitigation program description — if you are not fully STIR/SHAKEN compliant, you must describe the specific measures you have implemented
• Company contact information — the FCC uses this for enforcement outreach; stale contacts are a red flag
• Operating company number (OCN) and 499 Filer ID — these must match your current FCC registration records
• Certification by an authorized officer — the filing must be signed by someone with legal authority to bind the company

Any material change to your network architecture, call signing capabilities, or business structure since your last filing must be reflected in the recertification. Filing a copy of last year's submission without review is a compliance risk, not a compliance strategy.

Who Must File and When

The recertification obligation applies to all voice service providers required to be in the RMD, including:

• Originating providers (retail VoIP, CPaaS, UCaaS platforms)
• Intermediate providers and wholesale carriers
• Gateway providers handling international traffic entering the U.S. PSTN
• SIP trunk providers passing traffic to downstream carriers

The FCC has not established a single universal calendar date for RMD annual recertification across all providers. Recertification windows are tied to your original registration date and any subsequent FCC guidance issued for specific provider classes. Confirm your specific recertification deadline directly with the FCC's RMD portal and any current FCC orders or public notices. Do not rely on the assumption that your deadline matches another provider's.

What is certain: the FCC has demonstrated it will act against providers who are not current. In June 2026, the Commission cut SK Teleco's access to U.S. voice networks, a direct enforcement outcome tied to robocall compliance failures. That action signals the FCC is willing to use its full authority, not just issue warnings.

The Upstream Blocking Risk Is Real and Growing

The FCC's July 2026 robocall vetting mandate proceeding and its ongoing "know your upstream provider" rulemaking are reshaping how intermediate carriers evaluate their traffic relationships. Carriers are now expected to verify that every provider in their call path has a current, accurate RMD filing before accepting traffic.

If your Robocall Mitigation Database registration is expired or inaccurate, any carrier downstream can — and increasingly will — block your traffic without prior notice. The FCC has explicitly stated that carriers who block traffic from non-compliant providers are protected from liability for doing so.

For call centers, international operators entering the U.S. market, and wholesale carriers with high call volumes, even a 24-hour traffic block is a material financial event. Annual recertification is not overhead — it is risk management.

RMD Recertification Checklist

How RMD Recertification Connects to Your Broader FCC Compliance Calendar

RMD recertification does not exist in isolation. Voice providers operating in the U.S. carry a stack of annual and quarterly FCC obligations that must be managed in parallel. Upcoming hard deadlines include FCC Form 499-Q filings due August 3, 2026 (Q3) and November 2, 2026 (Q4), the annual CPNI Certification due March 1, 2027, and the FCC Form 499-A annual filing due April 1, 2027.

Providers who treat these as separate administrative tasks often find themselves scrambling. A coordinated compliance calendar — one that maps RMD recertification alongside 499 filings, CPNI certifications, and STIR/SHAKEN compliance obligations — is the operational standard for any provider serious about staying in good standing with the FCC.

Common Mistakes That Create Enforcement Exposure

• Filing last year's description verbatim without reviewing whether your network or signing status has changed
• Using a departed employee's contact information — enforcement letters that go unanswered accelerate FCC action
• Claiming full STIR/SHAKEN compliance when your network still has unsigned call paths
• Missing the recertification window entirely because no internal owner was assigned to track it
• Failing to update after a merger, acquisition, or network migration that changed your origination footprint

What Happens If You Miss Recertification

The FCC does not send reminders. If your filing lapses, your status in the RMD reflects non-compliance. Downstream carriers conducting due diligence — which the FCC now expects them to do — will see that status. The Commission has placed voice providers on robocall compliance plans and, in more serious cases, cut off network access entirely. The enforcement trajectory in 2026 is toward faster action, not more patience.

Beyond FCC action, an expired RMD filing can trigger contractual defaults with upstream carriers who require current RMD status as a condition of interconnection agreements.

Get Support for Your RMD Annual Recertification

STIRSHAKEN.AI provides technical and regulatory preparation support for voice providers navigating RMD annual recertification and the full FCC compliance stack. Our team understands the network layer — not just the paperwork — which means we can help you accurately represent your STIR/SHAKEN signing status, draft a defensible robocall mitigation program description, and coordinate your recertification with your broader telecommunications compliance services calendar.

If you are unsure whether your current RMD filing accurately reflects your network, or if you need to confirm your recertification deadline, reach out to STIRSHAKEN.AI. We work with VoIP providers, wholesale carriers, CPaaS platforms, and international operators entering the U.S. market — and we know what the FCC is looking for.