Autonomous system
AS19939 BCTELCO
Unclassified ARIN
Summary
Beaver Creek Telephone Company
telecom rural access residential
BCTELCO is the AS handle for Beaver Creek Telephone Company.
What it's used for
- The address space carries residential and local access traffic, evidenced by the reverse DNS record
ip-69-54-139-254.client.bct.orgwhich uses theclientsuffix typical of end-user connections. - The network announces a single IPv4 prefix,
69.54.128.0/20, comprising 4096 addresses, with no IPv6 prefixes in inventory. - With only 1 observed neighbour in RIS, the ratio of address space to peering partners indicates a small, local access network rather than a transit provider.
Notable
- The RDAP registrant for the announced prefix is
Beaver Creek Telephone Company, matching the registry holder and AS handle exactly. - The address inventory consists of a single contiguous /20 block, representing a compact and unified estate for this rural telephone company.
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.
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS33470 | Canby Telephone Association | 64 |
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 1 prefixes · 4.10K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 1 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS19939- Registry name
- BCTELCO
- Registrant
- Beaver Creek Telephone Company
- Abuse contact
- abuse@bctelco.com
- Registered
- 2001-03-06
- Last changed
- 2012-02-24
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Beaver Creek Telephone Company
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
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 · 1 valid, 0 with no ROA
- ROAs
- 1 authorising AS19939
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 1 naming AS19939
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: 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