S. 2666: Foreign Robocall Elimination Act
Sponsor
Ted Budd
Republican · NC
Foreign robocall networks get named and squeezed
Why it matters
Up to $100,000 is on the table for voice providers the FCC sees as risky, and providers tied to heavy unlawful robocall traffic could be publicly named. S. 2666 tries to make foreign scam-call networks easier to trace, expose, and shut out of the U.S. phone system.
Foreign robocalls are hard to stop because the path into the U.S. phone system can run through multiple carriers, multiple countries, and a lot of finger-pointing. S. 2666 responds by forcing the FCC, FTC, DOJ, and private-sector experts into one time-limited taskforce focused specifically on unlawful robocalls coming from outside the United States.
The practical change is that providers tied to suspicious robocall traffic could face public exposure, FCC enforcement, and in some cases a bond of up to $100,000 to stay in the robocall mitigation system.
The bill gives that taskforce a deadline-heavy schedule. The FCC must create it within 270 days of enactment, and the group must deliver recommendations within 360 days after it is formed on foreign robocalls, financial loss, identity theft, caller-ID authentication, blocking practices, and whether traceback results should be made public.
S. 2666 also tries to strengthen traceback — the process used to follow scam calls back through the network. It protects the registered traceback consortium from lawsuits for receiving, sharing, or publishing covered call information, and it lets the FCC or the consortium publish providers that refuse to cooperate or are found to originate or transmit substantial amounts of unlawful robocalls.
If the FCC uses those tools aggressively, the bill could change the economics for smaller or less-established voice providers that want access to U.S. call traffic but cannot show they are operating legitimately.
That is where the bond comes in. The FCC could require up to $100,000 from some providers filing certifications to the Robocall Mitigation Database, while carving out exemptions for providers it views as established and compliant, such as those with registration, state licenses, required federal contributions, or other signs of legitimate operations.
The bill does not promise that scam calls disappear from your phone. It does create a faster process for naming weak links in the call chain and raising the cost of staying in that chain if the FCC thinks a provider is part of the problem.
Bill Progress
Latest Action · Aug 10, 2026
Passed the Senate, received in House
S. 2666 Bill Summary
What S. 2666 actually does.
A federal robocall taskforce goes on the clock
The FCC must create an interagency taskforce within 270 days after enactment, in consultation with the FTC and the Attorney General. It would include federal agencies plus seven private-sector representatives.
Private-sector players get seven seats at the table
Those seven seats are reserved for three robocall experts, one traceback consortium representative, one marketing caller, one non-marketing business or nonprofit caller, and one consumer advocate with robocall expertise.
The report has to answer where foreign scam calls start
Within 360 days after the taskforce is established, it must recommend ways to combat unlawful robocalls from outside the United States. The bill specifically tells it to study financial loss, identity theft, foreign points of departure, STIR/SHAKEN, blocking practices, and whether more public traceback disclosure makes sense.
Traceback work gets legal protection
The registered traceback consortium would be shielded from lawsuits for receiving, sharing, or publishing covered information tied to suspected fraudulent, abusive, unlawful, or illegally spoofed calls, including call detail records and provider information.
Providers can be publicly named
The FCC or the traceback consortium could publish the names of providers that refuse to cooperate with traceback efforts or are found to originate or transmit substantial amounts of unlawful robocalls. The FCC could then use that list as a basis for enforcement.
Riskier providers could face a $100,000 bond
The FCC could require a bond of up to $100,000 from providers filing certifications to the Robocall Mitigation Database if the agency decides it is needed to protect the system's integrity. The bill also directs the FCC to create exemptions for providers that appear established and compliant.
Who benefits from S. 2666?
People who keep getting scam calls
If the bill works as supporters intend, you could see faster action against the providers that help foreign robocalls reach U.S. phones. The taskforce is specifically told to study financial loss and identity theft from calls coming from abroad.
Investigators trying to trace scam-call routes
The FCC, FTC, DOJ, and the registered traceback consortium would get a more formal structure for sharing information and producing recommendations on where enforcement is failing.
Established voice providers with legitimate operations
Providers that can show they are established and compliant may avoid the new bond requirement if the FCC grants exemptions based on registration, licensing, required contributions, or similar indicators.
Who is affected by S. 2666?
Voice providers in the robocall mitigation system
Some providers could be asked to post a bond of up to $100,000 before filing or maintaining a certification, depending on how the FCC applies the new authority.
Providers that do not cooperate with traceback requests
They could be publicly listed by the FCC or the traceback consortium, which could expose them to reputational harm and FCC enforcement.
Providers linked to heavy unlawful robocall traffic
If the FCC or consortium finds they originate or transmit substantial amounts of unlawful robocalls, they could be named publicly and face enforcement based on that finding.
Businesses and nonprofits that call consumers legally
They get representation on the taskforce, but they could also be affected later if the report leads to tighter blocking, authentication, or traceback expectations for legitimate callers.
S2666 Legislative Journey
House: Action Taken
Aug 10, 2026
Held at the desk.
Passed 4412-4414
Aug 3, 2026
Passed Senate with an amendment by Unanimous Consent. (consideration: CR S4412-4414; text: CR S4412-4414)
+1 more action this day
Committee Action
Jun 1, 2026
Committee on Commerce, Science, and Transportation. Reported by Senator Cruz with an amendment in the nature of a substitute. With written report No. 119-122.
Passed Committee
Oct 21, 2025
Committee on Commerce, Science, and Transportation. Ordered to be reported with an amendment in the nature of a substitute favorably.
Committee Action
Aug 1, 2025
Read twice and referred to the Committee on Commerce, Science, and Transportation.
About the Sponsor
Ted Budd
Republican, NC · 9 years in Congress
Committees: Joint Economic Committee, Small Business and Entrepreneurship, Commerce, Science, and Transportation
View full profile →
Cosponsors (3)
This bill has 3 cosponsors: 2 Democrats, 1 Republican, reflecting bipartisan support. Cosponsors represent 3 states: Georgia, Ohio, Vermont.
Committee Sponsors
Commerce, Science, and Transportation Committee
0 of 28 committee members cosponsored
No committee members have cosponsored this bill
15 Republicans across this committee haven't cosponsored yet. Mobilize their constituents
What laws does S. 2666 change?
2 changes
Sections Amended
Section 13(d) of Pallone-Thune TRACED Act (Public Law 116-105; 133 Stat. 3287)
adding at the end the following: ``(3) Immunity for receiving, sharing, and publishing trace back information
Section 13(e) of Pallone-Thune TRACED Act (Public Law 116-105; 133 Stat. 3287)
read as follows: ``(e) List of Voice Service Providers
S. 2666 Quick Facts
- Committee
- Commerce, Science, and Transportation
- Chamber
- Senate
- Policy
- Science, Technology, Communications
- Introduced
- Aug 1, 2025
Passed the Senate, received in House
Aug 10, 2026
Official Sources
Official Congress.gov page for the Foreign Robocall Elimination Act with bill text, actions, and status.
The bill’s bond authority applies to providers filing certifications in the FCC’s Robocall Mitigation Database.
FCC’s main consumer and enforcement explainer for robocalls, relevant to the bill’s anti-robocall framework.
The bill specifically directs the taskforce to study caller-ID authentication and whether STIR/SHAKEN is adequate for foreign-originated robocalls.
The FTC is named in the bill as a consultation partner for the interagency taskforce on unlawful robocalls.
The bill involves the Attorney General and asks whether DOJ should have a dedicated office for robocall enforcement.
Official FCC initiative page covering coordinated agency action and enforcement against unlawful robocalls.
The bill defines the traceback consortium by reference to section 13(d) of the TRACED Act, making the public law text directly relevant.
The bill defines unlawful robocalls by reference to 47 U.S.C. 227, the core federal statute governing many robocall restrictions.
S. 2666 Common Questions
Could S. 2666 make some phone providers post a $100,000 bond?
Yes. S. 2666 lets the FCC require a bond of up to $100,000 from some providers in the Robocall Mitigation Database if the agency says it is needed to protect the system.
Can the FCC publicly name providers tied to unlawful robocalls?
Yes. S. 2666 says the FCC or the registered traceback consortium could publish providers that refuse traceback cooperation or are found to carry substantial unlawful robocall traffic.
Would the FCC be able to punish providers based on that public list?
Yes. The bill says the FCC may use that published list as a basis for enforcement against providers that refuse traceback cooperation or are tied to substantial unlawful robocalls.
Does S. 2666 protect robocall traceback groups from lawsuits?
Yes. The bill says no cause of action can be brought against the registered traceback consortium for receiving, sharing, or publishing covered robocall information.
How fast would the new robocall taskforce have to start?
The FCC would have 270 days after enactment to set it up. After that, the taskforce would have 360 days to send its recommendations to Congress and federal agencies.
What would the robocall taskforce actually study?
It would study foreign robocalls, financial loss, identity theft, where the calls originate, whether STIR/SHAKEN works well enough, blocking best practices, and whether traceback results should be public.
Who could avoid the new robocall bond requirement?
The bill tells the FCC to create exemptions for providers when a bond is not needed. That could include providers with registration, state licenses, required federal contributions, or other signs of legitimate operations.
Does S. 2666 create a permanent new robocall office?
Not in this bill. It creates a temporary taskforce that ends 90 days after its report, though the report must consider whether DOJ should have a dedicated office for robocall enforcement.
Based on S. 2666 bill text
S. 2666 Bill Text
“To direct the Federal Communications Commission to establish a taskforce on unlawful robocalls, and for other purposes.”
Source: U.S. Government Publishing Office
Get notified when S. 2666 moves
Committee votes, floor action, cosponsor changes — straight to your inbox.
Bill alerts + Legisletter's monthly briefing. Unsubscribe anytime.
Science, Technology, Communications Bills
9 related bills we're tracking
AM Radio for Every Vehicle Act of 2025
Motion to reconsider laid on the table Agreed to without objection.
Sep 15, 2026
Scientific Integrity Act
Referred to the House Committee on Science, Space, and Technology.
Feb 6, 2025
Kids Online Safety Act
Committee on Commerce, Science, and Transportation. Ordered to be reported with an amendment in the nature of a substitute favorably.
Aug 5, 2026
Sunshine Protection Act of 2025
Received in the Senate and Read twice and referred to the Committee on Commerce, Science, and Transportation.
Jul 15, 2026
GUARDRAILS Act
Referred to the Committee on Energy and Commerce, and in addition to the Committee on the Judiciary, for a period to be subsequently determined by the Speaker, in each case for consideration of such provisions as fall within the jurisdiction of the committee concerned.
Mar 20, 2026
Artificial Intelligence Civil Rights Act of 2025
Referred to the Committee on Energy and Commerce, and in addition to the Committee on Oversight and Government Reform, for a period to be subsequently determined by the Speaker, in each case for consideration of such provisions as fall within the jurisdiction of the committee concerned.
Dec 2, 2025
TAKE IT DOWN Act
Became Public Law No: 119-12.
May 19, 2025
States' Right to Regulate AI Act
Read twice and referred to the Committee on Commerce, Science, and Transportation.
Dec 17, 2025
ACERO Act
Received in the Senate and Read twice and referred to the Committee on Commerce, Science, and Transportation.
Feb 24, 2026
Trending Right Now
Bills gaining momentum across Congress
761st Tank Battalion Congressional Gold Medal Act
Referred to the Committee on Financial Services, and in addition to the Committee on House Administration, for a period to be subsequently determined by the Speaker, in each case for consideration of such provisions as fall within the jurisdiction of the committee concerned.
Feb 26, 2025
Federal Firearms Licensee Protection Act of 2025
Referred to the House Committee on the Judiciary.
Mar 3, 2025
Therapeutic Fraud Prevention Act of 2025
Referred to the House Committee on Energy and Commerce.
May 7, 2025
Tracking Science, Technology, Communications in Congress? Monitor bills, track cosponsor momentum, and launch advocacy campaigns — all from one advocacy platform.