Unwanted-call reports, by week and reporting date.

How to read a complaint count

Illustrative example, not an observed result: 100 records could include repeat reports by the same filer. The number alone does not tell us whether there were 100 people, 100 distinct calls or any verified violations. If 60 records described a recorded voice, the reported share would be 60 ÷ 100 = 60% of records—not 60% of all calls received.

A lower count next week could reflect calls, reporting choices, release delays or several factors. These data do not separate those causes.

Florida reporting context: August 3–30, 2026

A focused comparison of four seven-observed-date windows, not a complete calendar-month total. Florida is the state recorded in these unverified reports, not the caller's location. Counts are not adjusted for population and do not measure residents' risk.

Florida counts range from 6,253 to 6,717 across these windows. That variation is descriptive only. Download the comparison inputs; see the release manifest below for source files.

Download, check and cite

Download the weekly CSV, complete aggregate JSON, input manifest and release hashes, and calculation script. The reproduction notes define the fields, coverage and deduplication method. Downloads contain aggregates, not individual report records.

Suggested citation: Spam Text Relief, “Unwanted-call reporting data,” methodology full-row-max-multiplicity-v2 / paired-week-series-v2, data through 2026-10-04; cite this page and record your access date. Primary sources are the FTC and FCC; this publication's interpretation is separate from theirs. No agency endorsement is implied. See the dataset reuse terms below.

Dataset reuse

Spam Text Relief’s original FTC and FCC aggregate compilations, including those accompanying earlier weekly analyses, are available under Creative Commons Attribution 4.0 International (CC BY 4.0), to the extent the publication holds copyright or similar rights in them. You may share and adapt these compilations, including commercially, subject to the license terms.

When attribution is required, credit Spam Text Relief, link to the dataset page and the license, and indicate any changes, in a reasonable manner. For a useful citation, also identify the dataset and its data-through date. An attribution for an adaptation might read: “Spam Text Relief, Unwanted-call reporting data, CC BY 4.0; adapted,” with the relevant date and links.

This license does not claim ownership of agency records or restrict public-domain material. Underlying FTC and FCC releases retain their own rights status and source terms. The grant covers the publication’s dataset contributions, not its article prose, branding or third-party material. Neither agency endorsement nor endorsement of your reuse is implied.

Coverage, missing weeks and backfill

Only FTC weeks with records on all seven reporting dates enter this chart. This observation rule is not proof that every release has arrived. Counts remain provisional and may change with additional or revised releases. Identical rows within one release are retained; overlapping full rows across releases use the largest observed multiplicity. Without a stable report identifier, this is an explicit deduplication assumption, not a count of unique complaints or people.

Weeks excluded for fewer than seven observed dates: 2025-09-29, 2025-11-10. Weeks unavailable in the local input collection: 2025-10-06, 2025-10-13, 2025-10-20, 2025-10-27, 2025-11-03. Missing local data does not establish that the FTC published nothing. Chart lines break over missing intervals; missing FCC counts are not zero.

Calculations rebuilt October 9, 2026. Input retrieval dates, where known, are separate from this calculation date. The revision history is on the corrections page.

Selected weeks have a separate write-up: what the totals were, what people said the calls were about, where reports concentrated, and what the numbers cannot support.

• Week of August 17, 2026Week of August 17, 2026: 59,836 unwanted-call reports to the FTC67% of records were marked recorded-message or robocall. Counts differed between the highest and lowest reporting dates by 7.7×. These are unverified reports, not unique people or a measure of calls placed.
• Week of August 10, 2026Week of August 10, 2026: 58,658 unwanted-call reports to the FTC68% of records were marked recorded-message or robocall. Counts differed between the highest and lowest reporting dates by 6.4×. These are unverified reports, not unique people or a measure of calls placed.
• Week of August 3, 2026Week of August 3, 2026: 55,660 unwanted-call reports to the FTC68% of records were marked recorded-message or robocall. Counts differed between the highest and lowest reporting dates by 7.4×. These are unverified reports, not unique people or a measure of calls placed.