Monthly Robocall Intelligence Report

August 2026 Unwanted-Call Intelligence Report

A current snapshot of the numbers and complaint activity visible in CallSlayer Intelligence—and what the evidence does and does not establish.

Published August 3, 2026 · FTC data through July 30, 2026 · FCC data through August 1, 2026

The snapshot

The scale of reported unwanted-call activity

Distinct reported numbers301,433Appearing in at least one published complaint aggregate
FTC reports · latest 30 days223,740Reports in the current 30-day window
FCC originating mentions · latest 180 days2,595Complaints naming an originating number
FCC advertiser mentions · all loaded data239,891May overlap originating-number and other complaint categories

What the data says

Three useful findings from the current snapshot

01

Complaint activity is spread across a very large number set.

301,433 distinct numbers appear in the combined aggregate. That breadth is consistent with a calling environment shaped by rotating numbers, distributed campaigns, reassigned numbers, and caller-ID spoofing.

02

Recent complaint volume remains substantial.

The latest 30-day FTC window contains 223,740 reports. This is a volume indicator, not a count of proven violations or unique calling organizations.

03

Originating and advertiser numbers answer different questions.

FCC complaints can identify the number shown to the consumer and a separate advertiser number. Those fields can overlap, and either can be incomplete or spoofed, so CallSlayer keeps them separate.

Interpretation

A number match is a lead, not the whole answer

A complaint match can show that other consumers reported the displayed number. Carrier, caller-name, CallSlayer observation, website, message, and transcript clues can add context. Identifying the responsible company still requires evidence from the actual call or text because caller ID can be spoofed.

Search a phone number

What this report cannot establish

The limits are part of the analysis

  • A complaint is an unverified report, not a legal or regulatory finding.
  • One caller or campaign can use multiple numbers, and one displayed number can be spoofed.
  • FTC and FCC fields use different definitions and reporting windows, so their totals should not be added as if they were identical measures.
  • This first report is a baseline. It does not claim month-over-month movement without a comparable prior snapshot.

Methodology

How CallSlayer produced this report

Counts are aggregated from public FTC and FCC complaint datasets. A complaint is an unverified report, not a finding of wrongdoing.

  1. Normalize published phone-number fields into a consistent US number key.
  2. Aggregate FTC report counts and FCC originating- and advertiser-number mentions separately.
  3. Retain source-specific reporting windows and dataset dates.
  4. Publish only aggregate statistics and number-level intelligence; no CallSlayer user identity or private evidence appears in this report.

Coverage period: October 31, 2014 through August 1, 2026.

Dataset dates: FTC July 30, 2026; FCC August 1, 2026.