The Robocall Mitigation Database: A Small Provider’s Filing Checklist
- Every voice service provider must certify in the Robocall Mitigation Database, whether they’ve implemented full STIR/SHAKEN or a mitigation program instead.
- Your filing is a self-certification — it needs to match what’s actually true about your network, not what was true when you first filed.
- Downstream providers can refuse traffic from anyone missing from the database, so an outdated or missing filing is a real operational risk.
- Re-certifying takes minutes once you know what’s changed — the hard part is remembering to do it.
- Check your filing against your network today, update it if you’ve since implemented real signing, and set a recurring annual reminder to review it going forward.
The Robocall Mitigation Database doesn't get the same attention as the STIR/SHAKEN certificate itself, but it's just as mandatory — and just as easy to let go stale.
What the Database Actually Requires
Every voice service provider has to certify in the FCC's Robocall Mitigation Database, describing whether they've implemented STIR/SHAKEN, a robocall mitigation program, or both. This isn't a one-time box to check — it's a certification that's supposed to describe your network accurately, on an ongoing basis.
Why an Outdated Filing Is a Real Risk
Downstream providers are required to stop carrying traffic from anyone missing from the database or whose filing is clearly inaccurate. An outdated filing — one that still describes a mitigation program you've since replaced with real STIR/SHAKEN signing, for example — isn't just a paperwork problem. It's the kind of gap that can surface at the worst possible time, during an audit or a downstream provider's own compliance review.
A Short Filing Checklist
- Does your filing match reality today? If you've implemented STIR/SHAKEN since you last filed, your RMD entry should say so.
- Is your contact information current? A stale contact on file delays resolution if a downstream provider flags an issue.
- Have you changed OCNs or added new ones? Each one needs its own accurate representation in your filing.
- When did you last actually look at it? If the honest answer is "when I first filed," it's worth a fresh review.
Conclusion
The Robocall Mitigation Database is a living document, not a one-time form. A few minutes checking it against your current network every so often is far cheaper than finding out it's wrong when a downstream provider blocks your traffic.
This article is provided for general informational purposes only and does not constitute legal or compliance advice. Consult a qualified attorney or compliance professional about your organization’s specific obligations under FCC rules and the STIR/SHAKEN framework.
Need a STIR/SHAKEN certificate?
Telonium is an approved STI-CA — request your first certificate today.