Autonomous system
AS7752 THRES
Residential ARIN Cable/DSL/ISP
Summary
Threshold Communications
isp enterprise legacy
Autonomous System 7752 (THRES) belongs to Threshold Communications, Inc., a Redmond, Washington telecom provider serving businesses in the Seattle area and the wider Pacific Northwest.
What it's used for
- Providing business connectivity and communications: dedicated internet access, broadband and 4G/5G links, hosted PBX and SIP trunking, colocation, and managed cloud/security services.
- Announcing roughly 9,000 IPv4 addresses — chiefly
209.189.192.0/19, its own ARIN allocation — plus a2604:5000::/36IPv6 block.
Notable
- Reverse DNS across the entire range follows one generic pattern,
209-189-NNN-NNN.ip.threshinc.net, with backbone routers named on the same domain (br01.sttlwawb.ip.threshinc.net— a Seattle, WA border router). There are no DSL, cable, PPPoE or dynamic-pool naming conventions anywhere in the space, which is the clearest signal that this is not an eyeball network. - Read it as a B2B provider: addresses here sit at company offices, at customer sites and in colocation racks, not in homes. The company's published customer list is enterprises and public agencies rather than consumers.
Interesting
- The generic per-IP reverse-DNS pattern is common to both business ISPs and residential ones, so it is easy to misread on its own. What settles it here is the absence of subscriber-pool naming plus the operator's actual product line — a reminder that rDNS is most useful for what it does not say.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Seattle Internet Exchange | Seattle, United States | 206.81.80.28 |
Transit providers
11 upstream, 1 downstream and 18 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-26, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 4 prefixes · 8.96K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 5 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS7752- Registry name
- THRES
- Registrant
- THRESHOLD COMMUNICATIONS,INC.
- Abuse contact
- arin-abuse@thresholdcommunications.com
- Registered
- 1997-01-02
- Last changed
- 2012-06-20
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Threshold Communications
- Also known as
- THRESHINC
- Network type
- Cable/DSL/ISP
- Scope
- North America
- Traffic ratio
- Balanced
- Peering policy
- Open
- IRR as-set
AS-THRESHINC- Present at
- 1 exchanges
- Facilities
- 1 facilities
- Website
- http://www.thresholdcommunications.com/
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 5 valid, 0 with no ROA
- ROAs
- 5 authorising AS7752
- ASPA
- no ASPA record
- IRR
- 100% registered · 5 of 5 announcements
- Route objects
- 9 naming AS7752
Reputation
Classification and threat
Residential Fixed-line consumer ISP. Addresses here are homes.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 445 networks and 1,817 prefixes, as published 2026-10-27. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere