Canadial Know Who Called

(202) 735-3108

Medium risk

(202) 735-3108 is likely an unwanted sales call: 3 FTC complaints, 33% recorded messages.

Report this number
Did (202) 735-3108 call you?
3
FTC complaints
0
Community reports
33%
Recorded messages
Sep 5, 2026
Latest report

Complaint history

3 FTC complaints between Sep 4, 2026 and Sep 5, 2026.

All 3 FTC complaints are about calls in Sep 2026.

FTC complaints are filed by consumers with the U.S. Federal Trade Commission's Do Not Call registry; they aren't verified by the FTC or by us.

What callers claimed

Complaint categories chosen by FTC complainants:

  • Not specified / other 3 · 100%

Who called

The number's block is assigned to Bandwidth.com CLEC, LLC.

Is it a debt collector?

Nothing says it is: none of its 3 complaints describe debt collection.

Nearby numbers in 202-735

109 numbers in 202-735 have 170 FTC complaints between them (45% robocalls), 3 of them about (202) 735-3108. The commonest categories in the block: Dropped call or no message (17%), Calls pretending to be government, businesses, or family and friends (9%).

The closest reported numbers on either side of (202) 735-3108, in number order.

All reported numbers in 202-735 →

When the calls came

Time of day of 3 calls; most often the 4 p.m. hour (2):

12a 6a 12p 6p

Day of the week of 3 calls; most often Friday (2):

Sun Mon Tue Wed Thu Fri Sat

The date and time of the call as complainants entered them on the FTC form; the time zone isn't recorded. Times entered as exactly midnight or noon are left out (they're usually the form's default).

Location

Rate centre (NANPA abbreviation)
WSHNGTNZN1, DC, USA
Block assigned to
Bandwidth.com CLEC, LLC

From the North American Numbering Plan Administrator (Nov 3, 2026). This is who the number block was assigned to; numbers can be moved between carriers, and caller IDs can be faked.

None of 3 complainants have area code 202, the number's own. The calls reached people elsewhere, so this isn't a local caller to them.

Most FTC complainants were in Ohio (2 of 3); others in Louisiana (1). Statewide, Ohio ranks #20 of the 50 states and DC for Do Not Call complaints per resident: 89,948 in the last 12 months, 755.8 per 100,000 people. Spam calls in Ohio.

Where FTC complainants were located (U.S. states):

  • Ohio 2 · 67%
  • Louisiana 1 · 33%

Complainants' cities:

Baton Rouge, LA (1) · Dublin, OH (1) · Englewood, OH (1)

As typed on the FTC form, with spelling variants merged; complaints without a city aren't counted.

Area code 202: where it is, time zone, spam calls →

Searches on Canadial

Loading…

Real visits to this page, counted once per visitor per day.

Did (202) 735-3108 call you?

Loading…

Answers from visitors, one per person per month (asked at the top of the page).

Report (202) 735-3108

Tell others what the call was about. Reports appear on this page; no account needed.

Recent community reports

No community reports yet. Be the first to describe this call.

What to do

Questions about (202) 735-3108

Who called me from (202) 735-3108?
No complaint names the caller. The number is in a block assigned to Bandwidth.com CLEC, LLC (rate centre WSHNGTNZN1, DC) (NANPA, Nov 3, 2026); numbers can move between carriers, so the caller's provider may differ.
Is (202) 735-3108 a scam?
Canadial rates it medium risk, from 3 complaints, latest Sep 5, 2026, 33% robocalls.
Is (202) 735-3108 a debt collector or collection agency?
Nothing says it is: none of its 3 complaints describe debt collection.
Should I call (202) 735-3108 back?
No. Calling back can confirm that your line is answered. If the caller claimed to be a company or agency you deal with, contact it on a number you find yourself.
How many times has (202) 735-3108 been reported?
3 complaints to the U.S. FTC's Do Not Call registry between Sep 4, 2026 and Sep 5, 2026.
When does (202) 735-3108 call?
In FTC complaints, the most common time was the 4 p.m. hour (2 of 3 calls with a time); the most common day was Friday (2 of 3).

Data updated: FTC complaints through Nov 13, 2026; numbering records as of Nov 3, 2026; community reports live. How this page is built.