What Happens If You Ignore a Traceback Request?
Ignoring a traceback feels like a minor risk. It isn't.
The FCC removed more than a thousand voice providers from the Robocall Mitigation Database in 2025 alone. Some of those providers never saw it coming. Others ignored every warning along the way, right up until removal took effect.
That's the real lesson buried in this year's enforcement numbers. Non-cooperation doesn't trigger an instant penalty. It triggers a defined, escalating process instead. The FCC has used that process repeatedly against real carriers, some of them well known names in wholesale VoIP.
This article walks through that process step by step. We'll show exactly what triggers each stage of the ladder. We'll also show what it actually costs a carrier that lets a single missed traceback reach the top.
The Escalation Ladder, Step by Step
Non cooperation doesn't trigger an immediate penalty. It triggers a sequence instead. Each step carries its own consequences before the next one begins.
It starts quietly. The ITG classifies a provider as non cooperative internally. This classification is based on a pattern of factors, not a single event.
Those factors include routinely missing traceback deadlines. They also include serving as the originating network for illegal robocalls. Acting as a US point of entry for foreign fraud counts too, as does repeatedly failing to locate records.
This ladder is designed to give carriers multiple off ramps. Every stage represents a genuine chance to correct the course. Carriers who end up fully disconnected almost always ignore several warnings in a row.
Non-cooperation → Escalation: The ladder has multiple off-ramps
| Stage | Name | Description | Off-ramp |
|---|---|---|---|
| 01 | Internal classification | The ITG identifies a pattern of non-cooperation based on recurring behaviour rather than treating every isolated issue as an automatic escalation. | Correct the pattern |
| 02 | Pattern persists | Repeated missed deadlines, recurring inability to locate records, originating illegal robocalls or acting as a foreign traffic entry point can strengthen the non-cooperative pattern. | Fix the root cause |
| 03 | External pressure | A sustained pattern becomes increasingly difficult to treat as an isolated operational failure. Regulatory and industry attention can intensify as the provider continues to appear in problematic traffic chains. | Demonstrate cooperation |
| 04 | Network consequence | Continued failure to correct course can ultimately lead to severe downstream consequences, including loss of practical access to the US network. | No easy off-ramp |
What the ladder is designed to do: Create repeated opportunities for a carrier to identify the problem, improve its controls and demonstrate cooperation before consequences become more severe.
The practical lesson: The risk is cumulative. Repeated failures matter because they can transform individual operational problems into a broader pattern of non-cooperation.
The safest place on the ladder is not the first step. It is the point where the carrier chooses to step off.
From Internal Classification to Public Exposure
Once a provider is classified as non cooperative, that status doesn't stay hidden. The ITG can share it with government agencies and other carriers. In some cases, it becomes public information too.
This is a real shift. An internal compliance flag becomes something that shapes how other carriers view you. Accepting traffic from a flagged provider now carries its own compliance risk for them.
This is where the ladder's design becomes clear. The FCC isn't relying only on its own enforcement capacity. It's building a system where market pressure does much of the work first.
Visibility Shift: A private compliance flag can become a market signal
ITG classification → Information sharing → Counterparty concern → Reduced market access
| Step | What happens |
|---|---|
| 01 Internal status | ITG identifies the provider as non-cooperative. |
| 02 Shared signal | Information can reach agencies and other carriers. |
| 03 Market pressure | Other carriers may reassess the compliance risk of accepting your traffic. |
The enforcement multiplier: regulatory pressure can be reinforced by the carriers that control access to the network.
ITG Non Cooperative Classification and Public Reporting
The ITG's classification criteria are specific, not vague. A provider can be flagged for routinely missing traceback deadlines. Being the originating network for illegal robocalls is another trigger. So is acting as the entry point for illegal foreign traffic, or consistently failing to locate records.
This information doesn't just sit in a file. The ITG shares it through public reporting and with law enforcement partners. That means non cooperative status becomes visible to the agencies with real power to escalate.
Why Public Visibility Changes Everything
Public visibility removes the option of quietly ignoring a problem. Once your business appears in ITG reporting, pressure builds from multiple directions at once. The same is true if you're named in a state AG warning letter.
We've seen this play out at scale. In 2025, coordinated multistate task forces sent warning letters to dozens of providers at once. Each letter cited specific traceback notice counts tied to that provider.
One company named in an April 2025 letter had received almost 1,000 traceback notices since 2019. Those notices covered tax relief fraud, utility disconnect scams, and student loan schemes. That kind of history doesn't stay private once regulators start acting on it.
It becomes part of the public record too. Any future business partner, investor, or acquirer can find it with a basic search.
From Flag to Market Signal: Non-cooperative status can travel far beyond the ITG
- ITG classification — Provider identified as non-cooperative.
- Information shared — Visibility extends to agencies and industry participants.
- Counterparty risk — Other carriers have a reason to reassess the relationship.
- Public exposure — The history can become discoverable beyond the original investigation.
Why the signal compounds:
- Regulators — Can use the history when deciding whether further action is warranted.
- Carriers — May view continued traffic exchange as carrying additional compliance risk.
- Business stakeholders — Partners, investors and acquirers may encounter the record during diligence.
The important transition is: classification → visibility → market consequence.
State AG Warning Letters and the Multistate Task Force
State attorneys general are an increasingly active part of this picture. They operate through a coordinated body called the Anti-Robocall Multistate Litigation Task Force. This group has grown more aggressive with each passing year.
In August 2025, more than fifty bipartisan attorneys general launched Operation Robocall Roundup. They sent warning letters to 37 voice providers simultaneously. Each letter demanded the providers stop routing illegal robocalls through their networks.
The task force didn't stop at the 37 primary targets either. It also sent letters to more than 100 downstream providers. Those letters warned them they were doing business with providers breaking the law.
These Letters Aren't Symbolic
These letters aren't friendly reminders. They explicitly warn recipients they could face damages, civil penalties, and injunctions. The task force also shares its findings with federal partners, including the FCC.
That means a state warning letter can trigger federal enforcement directly. It isn't a separate, disconnected track. By late 2025, the task force had expanded beyond smaller gateway operators entirely.
It began targeting some of the largest voice infrastructure providers in the country. These providers allegedly routed billions of illegal robocalls despite thousands of traceback notices. The lesson for smaller carriers is simple. Size doesn't provide cover, and neither does distance from the original bad actor.
Downstream carriers received warning letters too, specifically for doing business with flagged providers. Your compliance exposure isn't limited to your own direct traffic. It extends to who you choose to accept traffic from.
State AG Enforcement Network: A warning letter can widen the compliance circle
| Step | What happens |
|---|---|
| Signal: Traceback history | Repeated traceback notices, illegal traffic patterns or problematic routing create an evidence trail. |
| State AG task force: Warning letter | The provider is placed on notice and warned that continued conduct can create exposure to civil enforcement. |
| Exposure expands: Multiple audiences | Federal partners, downstream carriers and other stakeholders may now have reason to scrutinise the relationship. |
Operation Robocall Roundup · August 2025
- 50+ bipartisan attorneys general
- 37 voice providers receiving warning letters
- 100+ downstream providers also warned
- 1,000 traceback notices cited for one provider
- Primary target: Provider accused of routing illegal traffic — direct enforcement attention.
- Downstream target: Provider doing business with flagged traffic sources — counterparty relationship becomes relevant.
Why this matters: state enforcement does not have to follow the same path as an FCC investigation. A state warning letter can create a parallel record, reach federal partners and place pressure on the carriers connected to the traffic.
Cure or Explain Orders and the Path to RMD Removal
Before removing a provider from the RMD, the FCC usually offers a chance to fix things. This process is known as a cure or explain order. It gives providers a real off ramp before the harshest consequence.
The process typically starts with a Notification of Suspected Illegal Traffic. If the issue isn't resolved, an Initial Determination Order and Order to Show Cause follows. That order gives the provider a defined window, commonly 14 days.
Within that window, the provider must demonstrate compliance or explain the deficiency. This structure exists because the FCC's stated goal is compliance, not punishment. A provider that responds meaningfully during the cure window can often avoid removal entirely.
What Happens When the Cure Window Closes?
If the provider doesn't respond adequately, removal from the RMD follows. Once a provider loses RMD certification, every other carrier must stop accepting its direct traffic. This is a hard rule, not a suggestion.
The FCC's 2025 record shows this process moving from warning to consequence repeatedly. A September 2025 group order gave twelve providers 14 days to cure outstanding deficiencies. An earlier warning had already gone unheeded in each case.
When the cure window closed without adequate response, removal followed. Separately, an August 2025 Final Removal Order cut off certifications for over 1,200 providers at once. Many of those providers had also failed to respond to tracebacks.
RMD removal isn't a fine you pay and move past. Every carrier in the US must stop accepting your direct traffic immediately. For a wholesale VoIP business, that's an operational shutdown, not a compliance cost.
Re-entry also isn't automatic. It requires prior approval from the FCC's Enforcement and Wireline Competition Bureaus. You can't simply refile a corrected certification on your own timeline.
RMD Enforcement Path: The cure window is the last operational off-ramp (14-day response window)
01 · Signal → 02 · Cure or Explain → 03 · Consequence
| Step | Name | Description |
|---|---|---|
| 01 · Signal | Notification of Suspected Illegal Traffic | The FCC identifies a suspected problem and puts the provider on notice. |
| 02 · Cure or Explain | Initial Determination + Order to Show Cause | The provider receives a defined opportunity to demonstrate compliance or explain the deficiency. |
| 03 · Consequence | RMD Removal | If the response is inadequate, certification is removed and direct traffic can no longer be accepted. |
The key decision point: The cure window is not merely a deadline. It is the provider's opportunity to preserve its RMD status before the network consequence becomes unavoidable.
- Adequate response: Demonstrate compliance, correct the deficiency, or provide a credible explanation within the defined window. → Potential off-ramp: remain certified.
- Inadequate response: Ignore the order, respond incompletely, or fail to cure the identified deficiency before the window closes. → Consequence: RMD removal.
After removal: US carriers stop accepting direct traffic · Re-entry is not automatic · Prior FCC approval required
Why the 2025 Enforcement Numbers Prove This Isn't Theoretical?
It's easy to assume the top rungs of this ladder are rarely reached. The FCC's actual 2025 enforcement record says otherwise. Individual providers faced their own dedicated removal proceedings throughout the year, not just group actions.
One provider acknowledged receiving a Notification of Suspected Illegal Traffic and an Initial Determination Order. It took no substantive action in response to either. It was ultimately prohibited from connecting to US networks entirely, with downstream providers ordered to block its traffic within 48 hours.
The Common Thread Across Every Enforcement Action
A consistent pattern emerges across these cases. Every provider that reached the final rung had multiple earlier chances to fix the problem. That usually included an initial warning, a formal notice, and a defined cure period.
State level warning letters often ran in parallel too. None of these providers were caught off guard by one missed deadline. Sudden disconnection only followed after repeated, documented warnings.
That's useful information for carriers building their own compliance posture. The ladder gives you real time to course correct at nearly every stage. Carriers who end up fully cut off almost always ignored multiple warnings across multiple stages.
There's also heavy overlap between the federal and state tracks. Both frequently draw from the same underlying data, often the same ITG traceback history. A provider that resolves the underlying issue tends to see pressure ease on both fronts at once.
2025 Enforcement Pattern: The final consequence was rarely the first warning (example blocking window: 48h)
The important signal in the 2025 record is not only the number of removals. It is the repeated sequence of notice, opportunity, inaction, and escalation.
| Step | Name | Description |
|---|---|---|
| 1 | Warning | Suspected illegal traffic is identified and the provider is put on notice. |
| 2 | Formal notice | An Initial Determination and Order to Show Cause creates a defined response opportunity. |
| 3 | Cure window | The provider can demonstrate compliance, correct the issue, or explain the deficiency. |
| 4 | Network consequence | Failure to respond adequately can end in RMD removal and loss of practical network access. |
Course correction: One underlying fix can address multiple pressure points. Because federal and state scrutiny can draw on the same underlying traceback history, resolving the actual compliance problem can reduce pressure across both tracks.
Why cut-off happens: Escalation is cumulative, not instantaneous. The providers reaching the most severe outcome generally had several documented opportunities to respond before network access was restricted.
Compliance lesson for carriers: Treat every notice as a course-correction point. The earlier the underlying problem is fixed, the more options remain available.
What's Next in This Series
Understanding the full cost of non cooperation makes one thing clear. The traceback obligation isn't a box you check once. It's an ongoing responsibility that deserves a real process, not an ad hoc scramble.
The next article covers how to build that internal process before you need it. We'll cover designating a compliance contact and setting up proper call detail record retention. We'll also cover response templates that turn a frantic scramble into a routine task.
The carriers who avoid ever climbing this ladder treat traceback response as infrastructure. They don't treat it as an afterthought handled only when a request happens to land.