Skip to content

Area code 513 · Ohio

(513) 831-2600

513-831-2600 · 5138312600 · High complaint volume

Consumers have filed 28 complaints about calls from (513) 831-2600 with the Federal Trade Commission and the Federal Communications Commission, between Jan 15, 2025 and Oct 20, 2026. The most common topic is dropped call or no message (1 of 28 reports), and 7% of callers used a recorded message. Complaints came from 22 states, which is typical of mass-dialing campaigns.

28Total complaintsFTC 8 · FCC 20
5Last 30 daysLast 7 days: 1
7%Recorded messageof 28 reports that said
22States reportingMost: California

Complaint activity for (513) 831-2600

Complaints per day about (513) 831-2600, Jul 24, 2026 to Oct 21, 202612Jul 24, 2026: 0Jul 24Jul 25, 2026: 0Jul 26, 2026: 0Jul 27, 2026: 0Jul 28, 2026: 1Jul 29, 2026: 0Jul 30, 2026: 0Jul 31, 2026: 0Aug 1, 2026: 0Aug 1Aug 2, 2026: 0Aug 3, 2026: 0Aug 4, 2026: 0Aug 5, 2026: 0Aug 6, 2026: 0Aug 7, 2026: 0Aug 8, 2026: 0Aug 9, 2026: 0Aug 10, 2026: 0Aug 11, 2026: 0Aug 12, 2026: 0Aug 13, 2026: 0Aug 14, 2026: 0Aug 15, 2026: 0Aug 16, 2026: 0Aug 17, 2026: 0Aug 18, 2026: 0Aug 19, 2026: 0Aug 20, 2026: 0Aug 21, 2026: 0Aug 22, 2026: 0Aug 23, 2026: 0Aug 24, 2026: 0Aug 25, 2026: 0Aug 26, 2026: 0Aug 27, 2026: 0Aug 28, 2026: 0Aug 29, 2026: 0Aug 30, 2026: 0Aug 31, 2026: 0Sep 1, 2026: 0Sep 1Sep 2, 2026: 0Sep 3, 2026: 0Sep 4, 2026: 0Sep 5, 2026: 0Sep 6, 2026: 0Sep 7, 2026: 0Sep 8, 2026: 0Sep 9, 2026: 0Sep 10, 2026: 0Sep 11, 2026: 0Sep 12, 2026: 0Sep 13, 2026: 0Sep 14, 2026: 2Sep 15, 2026: 0Sep 16, 2026: 0Sep 17, 2026: 0Sep 18, 2026: 1Sep 19, 2026: 0Sep 20, 2026: 0Sep 21, 2026: 0Sep 22, 2026: 1Sep 23, 2026: 0Sep 24, 2026: 1Sep 25, 2026: 0Sep 26, 2026: 0Sep 27, 2026: 0Sep 28, 2026: 0Sep 29, 2026: 0Sep 30, 2026: 0Oct 1, 2026: 0Oct 1Oct 2, 2026: 1Oct 3, 2026: 0Oct 4, 2026: 0Oct 5, 2026: 0Oct 6, 2026: 0Oct 7, 2026: 0Oct 8, 2026: 0Oct 9, 2026: 0Oct 10, 2026: 0Oct 11, 2026: 0Oct 12, 2026: 0Oct 13, 2026: 1Oct 14, 2026: 0Oct 15, 2026: 0Oct 16, 2026: 0Oct 17, 2026: 0Oct 18, 2026: 0Oct 19, 2026: 0Oct 20, 2026: 1Oct 21, 2026: 0
Complaints per day about (513) 831-2600, Jul 24, 2026 to Oct 21, 2026

What callers from this number were about

Silent or dropped calls often come from automated dialers checking whether a line is active. Answering or calling back can confirm that your number is in use and lead to more calls.

Where the complaints came from

Cities named in complaints: Farmingdale, NY (1) · Pottstown, PA (1) · Charlotte, NC (1) · Fresno, CA (1) · Spring Hill, TN (1) · Atlanta, GA (1) · Tempe, AZ (1) · Washington, DC (1) · Minneapolis, MN (1) · Puyallup, WA (1) · Pueblo, CO (1) · Oakland Park, FL (1)

Latest complaints

Date filedConsumer locationTopicTypeSource
Oct 20, 2026Minnetonka, MNImpostor callsLive callerFTC
Oct 13, 2026GAOtherLive callerFTC
Oct 2, 2026Louisville, KYOtherRecorded messageFTC
Sep 24, 2026Bennett, NCDropped call or no messageLive callerFTC
Sep 22, 2026Odessa, TXOtherLive callerFTC
Sep 18, 2026San Leandro, CAOtherLive callerFTC
Sep 14, 2026Oakland Park, FLOtherLive callerFTC
Sep 14, 2026Puyallup, WAOtherLive callerFTC
Jul 28, 2026Washington, DCNot specifiedLive callerFCC
Mar 20, 2026Atlanta, GANot specifiedLive callerFCC
Mar 18, 2026Fresno, CANot specifiedLive callerFCC
Feb 27, 2026Pottstown, PANot specifiedLive callerFCC
Feb 25, 2026Cincinnati, OHNot specifiedLive callerFCC
Feb 20, 2026Portland, ORNot specifiedLive callerFCC
Jan 8, 2026Jamestown, KSNot specifiedLive callerFCC
Dec 23, 2025Clearwater, FLNot specifiedLive callerFCC
Dec 19, 2025Fairbanks, AKNot specifiedLive callerFCC
Aug 14, 2025Pueblo, CONot specifiedLive callerFCC
Aug 7, 2025Minneapolis, MNNot specifiedLive callerFCC
Aug 1, 2025Tempe, AZNot specifiedLive callerFCC
Jul 22, 2025Spring Hill, TNNot specifiedLive callerFCC
Jun 27, 2025Charlotte, NCNot specifiedLive callerFCC
Jun 26, 2025Farmingdale, NYNot specifiedLive callerFCC
May 15, 2025Aurora, CONot specifiedLive callerFCC
Apr 30, 2025Mobile, ALNot specifiedLive callerFCC

Showing the 25 most recent of 28 complaints.

Linked call-back numbers

In FCC complaints, consumers can record the number the caller asked them to call back. These links show how numbers are used together in the same campaign.

  • Callers from (513) 831-2600 gave out (610) 256-5788 (1 report)
  • Callers from (513) 831-2600 gave out (205) 747-9866 (1 report)

Number details

Formats
(513) 831-2600 · 513-831-2600 · +1 513-831-2600 · 5138312600
Area code
513 · Ohio
Rate center
Ltl Miami, OH
Originally assigned to
Cincinnati Bell (prefix 513-831, since 2026)
First and last complaint
Jan 15, 2025 – Oct 20, 2026

The carrier shown is the company the prefix was first assigned to by the numbering administrator. Numbers are often ported to other carriers, and caller ID can be faked, so the real caller may be unrelated to this carrier or to the person who owns this number.

How to report an unwanted call

  • Federal Trade Commission. Report telemarketing and robocalls at donotcall.gov or by calling 1-888-382-1222. These are the reports that feed most of this site.
  • Federal Communications Commission. File an unwanted call or text complaint at consumercomplaints.fcc.gov.
  • Your phone carrier. Most carriers offer free spam labeling and call blocking, and some let you forward spam texts to 7726 (SPAM).
  • Your state attorney general. Most states have a consumer protection office that takes complaints about telemarketing and scams.

Other reported numbers in area code 513

Phone numberComplaintsTopicLast reported
(513) 655-50213Impostor callsOct 20, 2026
(513) 278-68125OtherOct 19, 2026
(513) 637-75195Not specifiedOct 18, 2026
(513) 909-24094Energy, solar & utilitiesOct 17, 2026
(513) 909-25184Energy, solar & utilitiesOct 17, 2026
(513) 655-57963Dropped call or no messageOct 14, 2026
(513) 829-28003Dropped call or no messageOct 8, 2026
(513) 367-36503Impostor callsOct 4, 2026

See all reported numbers in area code 513 →

Is this your number?

If you own (513) 831-2600 and believe it is being spoofed, tell your carrier and keep records of the complaints you receive. You can also contact us through the site to add context to this page.