FCC Bars over 1,200 Providers for Non-Compliance with Robocall Protections

https://news.ycombinator.com/rss Hits: 8
Summary

FCC Bars Over 1,200 Providers from Network Access for Their Continued Non-Compliance with Robocall Protections WASHINGTON, August 25, 2025—Today, in the latest FCC action to protect Americans from illegal robocalls, the agency’s Enforcement Bureau removed over 1,200 non-compliant voice service providers from the Robocall Mitigation Database, effectively disconnecting them from U.S. phone network. These providers violated FCC rules by failing to maintain accurate Robocall Mitigation Database certifications, thereby shirking their obligations to protect consumers from illegal robocalls. Earlier this month, these companies received a final warning from the FCC when the Enforcement Bureau removed an initial tranche of 185 providers from the Database. Chairman Brendan Carr issued the following statement: “Robocalls are an all-too-common frustration—and threat—to Americans households. The FCC is doing everything in its power to fight back against these malicious and illegal calls. Providers that fail to do their duty when it comes to stopping these calls have no place in our networks. We’re taking action and we will continue to do so.” Additional Background Information: The FCC’s Robocall Mitigation Database is a critical tool through which the agency ensures providers are actively combatting robocalls and implementing STIR/SHAKEN caller ID authentication. Providers are required to certify that they have implemented STIR/SHAKEN on all IP-based portions of their networks. All providers must also submit robocall mitigation plans. Failure to meet these obligations may result in removal from the database and blocking of the provider’s traffic. Removed providers will only be permitted to refile in the database with express approval from the FCC’s Enforcement and Wireline Competition Bureaus. In December 2024, the Commission ordered 2,411 providers to cure their deficient filings or provide a reason why they should not be removed from the Robocall Mitigation Database. Today’s a...

First seen: 2025-08-25 16:14

Last seen: 2025-08-25 23:15