Autonomous system
AS36545 BLEDSOE
Unclassified ARIN
Summary
Bledsoe Telephone Cooperative
telecom residential cooperative tennessee
The AS handle BLEDSOE is operated by Bledsoe Telephone Cooperative Corporation.
What it's used for
- The address space carries residential and business internet access, evidenced by reverse DNS entries like
host-66-9-84-0.bledsoe.netand netnamesBTCTN-NET-1andBTCC-3. - The network announces 24,832 IPv4 addresses across 19 prefixes with only 2 observed neighbours, a ratio indicative of a local access provider rather than a transit carrier.
Notable
- All registrants in the RDAP sample are Bledsoe Telephone Cooperative Corporation, matching the AS holder.
- The address inventory consists of multiple /21, /22, /23, and /24 blocks within the 66.9.0.0/16, 66.11.0.0/16, 76.9.0.0/16, 98.143.0.0/16, and 207.144.0.0/16 ranges.
- The operator serves customers in Tennessee, providing cellular, internet, and data services.
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
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-17, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 20 prefixes · 24.83K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 20 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS36545- Registry name
- BLEDSOE
- Registrant
- Bledsoe Telephone Cooperative Corporation
- Abuse contact
- arin@bledsoe.net
- Registered
- 2006-01-26
- Last changed
- 2012-03-02
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- BLEDSOE
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
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
- 0% valid · 0 valid, 51 with no ROA
- ROAs
- 0 authorising AS36545
- ASPA
- no ASPA record
- IRR
- 69% registered · 35 of 51 announcements
- Route objects
- 17 naming AS36545
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
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,783 prefixes, as published 2026-10-17. 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