Autonomous system
AS14939 THRES
Residential ARIN Cable/DSL/ISP
Summary
Threshold Communications
isp hosting telecom
Two IPv6 blocks the size most providers get one of, against 512 IPv4 addresses.
What it's used for
- A communications provider's network. 512 IPv4 addresses across two prefixes, two IPv6 prefixes, and three observed BGP neighbours.
Notable
- The IPv6 announcements are
2604:5000:1000::/36and2604:5000:2000::/36, two pieces of one larger range announced separately. 67.206.179.0/24carries the netnameTHRESand199.191.62.0/24carriesTHRES-BLK-4.- That second netname counts to four, though only two blocks appear here.
- Three addresses answer as
199-191-62-64.threshinc.com, under a domain that shortens the company name differently again.
Interesting
- The imbalance between the protocols is the striking part. This provider announces fewer IPv4 addresses than a small office building might use, and enough IPv6 to number every device in a city twice over. That is not ambition; it is what the allocation policies of the two protocols produce when applied to the same company.
- Splitting one range into two announcements rather than one is a choice about traffic engineering, and it doubles this network's contribution to the global table for no change in what is reachable.
- A netname counting to four with two blocks visible means two more exist somewhere, unrouted or announced elsewhere. Counters in netnames are one of the few places the registry accidentally records what is missing.
- Three shortenings of one company name, across the handle, the netname and the domain, is the usual state of affairs here.
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 |
|---|---|---|
| Ninja-IX Phoenix | Phoenix, United States | 206.41.105.27 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 512 addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 4 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS14939- Registry name
- THRES
- Registrant
- THRESHOLD COMMUNICATIONS,INC.
- Abuse contact
- arin-abuse@thresholdcommunications.com
- Registered
- 2006-09-22
- Last changed
- 2012-06-20
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Threshold Communications AS14939
- Also known as
- THRESHINC-14939
- 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 · 4 valid, 0 with no ROA
- ROAs
- 4 authorising AS14939
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 4 naming AS14939
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: 442 networks and 1,773 prefixes, as published 2026-10-13. 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