All insights
FCC & Regulation

KYC and KYUP Are Coming: What the FCC Proposes to Require of Every Voice Provider's Customers and Upstream Providers

Today the FCC requires voice providers to know their customers but does not say how. Two pending proposals would change that: specific identity checks before a customer can place calls, five baseline duties for every upstream provider, four years of records, and a $2,500 per call base fine.

Who should read thisExecutives and compliance leaders at originating, wholesale, and gateway voice providers

First page of the source: FCC 26-27 (Know Your Customer) FCC 26-27 (Know Your Customer) Proposed base fine$2,500per call for KYC violations
Primary source · May 1, 2026 Open the FCC 26-27 (Know Your Customer)
The bottom line
  • Current rules require "affirmative, effective measures" to know your customers, but the FCC has never specified what they are. FCC 26-27 proposes minimum identity information before service starts.
  • FCC 26-32 proposes five baseline duties for every upstream provider: information collection, compliance review, verification, monitoring, and responsive action.
  • Both proposals would require records to be kept for four years, and the FCC proposes a $2,500 per call base forfeiture for know-your-customer violations.
  • These are proposals. Comment periods have closed, and final rules could follow at any time.

Where the rules stand today

Every originating voice provider must already “take affirmative, effective measures to prevent new and renewing customers from using its network to originate illegal calls, including knowing its customers.” Providers that receive traffic must take “reasonable and effective steps” to ensure an upstream provider is not using them to carry a high volume of illegal traffic. What the FCC has never done is say exactly what those measures are.

That has not stopped enforcement. The FCC has proposed multimillion-dollar fines for vetting it considered inadequate, as covered in our analysis of the Voxbeam and Telnyx cases. Two pending proposals would now turn the general duty into specific requirements.

Know Your Customer: FCC 26-27

Released May 1, 2026, this further notice asks whether providers should, at a minimum, obtain and retain each new and renewing customer’s:

  • name and physical address;
  • government-issued identification number; and
  • an alternate telephone number,

before granting access to service. For high-volume customers, including business and foreign customers, providers would also collect the intended use of the service and verify more: corporate formation records, good standing, and evidence of a real commercial presence.

The FCC tentatively concludes that certain red flags should alert a provider, such as a registered agent or virtual office as the address, a newly created website or email, and untraceable payment such as cryptocurrency. It also asks about re-verification when traffic patterns change, and whether an accredited third-party verification service should earn a safe harbor.

Know Your Upstream Provider: FCC 26-32

Released May 21, 2026, this further notice would replace the current “high volume” standard with a broader duty to take “affirmative, effective measures” against upstream providers transmitting illegal calls. It proposes five baseline duties:

  1. Information collection directly from the upstream provider;
  2. Compliance review, including its Robocall Mitigation Database filing;
  3. Information verification, such as confirming that phone numbers and email addresses are active;
  4. Monitoring, including ongoing call analytics; and
  5. Responsive action, up to refusing or discontinuing service.

The duties would apply before a new agreement, before a renewal, and whenever new evidence arrives. The same proposal would tighten STIR/SHAKEN attestation, covered in our analysis of attestation.

What it would cost to fall short

Penalties and paperwork. The FCC proposes to codify a $2,500 per call base forfeiture for know-your-customer violations. Both proposals would require records to be kept for four years, matching the four-year statute of limitations for spoofing. A provider that cannot produce the evidence would be judged as if the checks never happened.

Questions to answer now

Provider leaders should be able to answer the following with confidence:

Answering these questions takes evidence, not policy documents. The VoiceAlerts Compliance Team can review where you stand in a free 30-minute briefing.

Key dates

How VoiceAlerts helps

VoiceAlerts runs Know Your Customer and Know Your Upstream Provider verification as a managed service, monitors the traffic each customer and upstream provider sends, and keeps the four-year audit trail the FCC proposes.

  • Identity verification for new and high-volume customers
  • The five proposed upstream-provider duties
  • Records that would satisfy a four-year retention rule
Book a free 30-minute briefing Explore Compliance & Identity

Get FCC & voice-security alerts

Not ready for a briefing? We’ll send you the next rule change or attack that affects your calls.

By signing up you agree to be contacted by VoiceAlerts. See our Privacy Policy.

Common questions

What does the FCC currently require for Know Your Customer?

Under 47 CFR 64.1200(n)(4), originating providers must take affirmative, effective measures to prevent new and renewing customers from originating illegal calls, including knowing their customers. The FCC has not mandated specific measures.

What would the FCC's KYC proposal require?

FCC 26-27 seeks comment on requiring providers to obtain and retain, at a minimum, the name, physical address, government-issued identification number, and an alternate telephone number of new and renewing customers before service, with more verification for high-volume customers, and four years of records.

What is Know Your Upstream Provider (KYUP)?

The duty to make sure providers that send you traffic are not using your network for illegal calls. FCC 26-32 proposes five baseline duties: information collection, compliance review, information verification, monitoring, and responsive action, with records kept for at least four years.

How can VoiceAlerts help providers prepare for KYC and KYUP rules?

VoiceAlerts runs KYC and KYUP verification as a managed service, monitors the traffic customers and upstream providers send, and keeps a four-year audit trail, so a provider can show how it knows who it carries.

Sources

  1. docs.fcc.govFCC 26-27: Enhancing Know-Your-Customer Requirements, Further Notice of Proposed RulemakingReleased May 1, 2026
  2. federalregister.govFederal Register: Enhancing Know-Your-Customer Requirements (FCC 26-27)Comments due June 25, replies July 27, 2026
  3. docs.fcc.govFCC 26-32: Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN, Further Notice of Proposed RulemakingReleased May 21, 2026
  4. federalregister.govFederal Register: Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN (FCC 26-32)Comments due August 10, replies September 8, 2026

This article is for general information and is not legal advice. Proposed rules can change before adoption; check the FCC record for the final text.

Free 30-minute compliance briefing

Could you show the FCC how you know your customers?

Book a briefing with the VoiceAlerts Compliance Team. We compare your current customer and upstream vetting with what the FCC proposes.

  • Identity verification for new and high-volume customers
  • The five proposed upstream-provider duties
  • Records that would satisfy a four-year retention rule
Want the details first? Compliance & Identity
Explore the service

Book a 30-minute briefing

Tell us a bit about you. We'll reply within one business day.

By submitting, you agree to our Privacy Policy. We never share your information.

More insights

View all
First page of the source: FCC Fact Sheet and draft order FCC Fact Sheet and draft order Fail to certifyNo new numbersand possible revocation
FCC & Regulation

The FCC's November 19 Vote on Phone Number Access: What VoIP Providers Should Prepare

The FCC votes Nov. 19 on new national-security certifications for VoIP providers with direct access to numbers. What the draft requires and how to prepare.

VoiceAlerts Compliance Team Source date · 4 min read
First page of the source: FCC Public Notice DA 26-932 FCC Public Notice DA 26-932 Coming to FCC.govPublic gradesfor provider robocall protection
FCC & Regulation

The FCC's Robocall Scorecard: How Voice Providers May Soon Be Graded in Public

The FCC plans a public scorecard rating voice providers on robocall protection, including how often legitimate calls are wrongly blocked. What to know.

VoiceAlerts Compliance Team Source date · 2 min read
First page of the source: FCC 26-32 (KYUP and STIR/SHAKEN) FCC 26-32 (KYUP and STIR/SHAKEN) Illegal calls48%carried A-level attestation
FCC & Regulation

STIR/SHAKEN Attestation Under Scrutiny: Why the FCC Wants to Know What Stands Behind Every A-Level Call

Nearly half of illegal calls carry A-level STIR/SHAKEN attestation. The FCC proposes stricter attestation rules. What providers should know about A, B and C.

VoiceAlerts Compliance Team Source date · 3 min read