What is the Robocall Mitigation Database?
What is the Robocall Mitigation Database?
Section titled “What is the Robocall Mitigation Database?”Unwanted phone calls are among the top complaints from American consumers. To address this, the FCC created the Robocall Mitigation Database (RMDB) as part of its broader effort to reduce illegal robocalls across US carrier networks.
The RMDB is a public registry where voice service providers certify that they have implemented the required call authentication framework and are taking specific, measurable steps to prevent the origination of illegal robocalls from their network.
Who Must Register?
Section titled “Who Must Register?”Any organization that qualifies as a “voice service provider” under the Telephone Robocall Abuse Criminal Enforcement and Deterrence (TRACED) Act is required to register. The FCC defines this broadly to include:
- Providers of outbound voice services
- Providers of inbound voice services
- Intermediate providers supporting STIR/SHAKEN authentication
This covers most organizations that have purchased enterprise or retail voice services from a provider.
How to Access the RMDB
Section titled “How to Access the RMDB”The database is publicly accessible at the FCC Robocall Mitigation Database portal. You can search for registered providers or download the full database.
What Happens If a Carrier Doesn’t Register?
Section titled “What Happens If a Carrier Doesn’t Register?”Carriers that fail to register face significant consequences:
- The FCC may directly fine the non-compliant provider.
- Downstream carriers may refuse to accept any call traffic originating from providers not listed in the RMDB.
Providers that missed the registration deadline and did not correct it faced traffic blocking by downstream carriers.
What Makes a Robocall Mitigation Plan Sufficient?
Section titled “What Makes a Robocall Mitigation Plan Sufficient?”The FCC’s Enforcement Bureau reviews each provider’s submitted plan. While no single universal checklist exists, a sufficient plan must:
- Outline specific best practices being followed to significantly reduce illegal robocalls on the network.
- Align with the FCC’s published best practice guidelines.
- Include participation in standard industry traceback protocols.
Is STIR/SHAKEN the Same as Robocall Mitigation?
Section titled “Is STIR/SHAKEN the Same as Robocall Mitigation?”No. STIR/SHAKEN and the RMDB address the same underlying problem but are distinct requirements:
- STIR/SHAKEN is a technical framework for authenticating call identity at the carrier level.
- The RMDB is the regulatory registry where carriers certify their compliance with either STIR/SHAKEN or an equivalent mitigation program.
A carrier that has implemented STIR/SHAKEN must still register with the RMDB separately.
Will the RMDB Eliminate Robocalls?
Section titled “Will the RMDB Eliminate Robocalls?”The FCC expects the RMDB and STIR/SHAKEN requirements to significantly reduce illegal robocalls. However, the RMDB alone cannot eliminate the problem — it requires sustained cooperation from voice service providers, continued enforcement action by the FCC, and consumer-level tools to supplement carrier-side mitigation.
How SIPSTACK Meets These Requirements
Section titled “How SIPSTACK Meets These Requirements”SIPSTACK is registered in the Robocall Mitigation Database and complies with STIR/SHAKEN requirements. SIPSTACK’s platform uses real-time analysis to authenticate activity and support partners and customers in applying risk-appropriate call handling. Contact SIPSTACK for more information.