Autonomous system
AS19413 ROANOKE-CONNECT-ASN-1
Unclassified ARIN
Summary
Roanoke Connect
residential isp municipal fiber
ROANOKE-CONNECT-ASN-1 is operated by Roanoke Connect, the broadband division of Roanoke Electric in Virginia.
What it's used for
- The address space carries residential and business broadband services, evidenced by netnames such as
RCHL-6andROANOKE-CONNECT-IPV4-BLOCK-1. - The AS announces 8192 IPv4 addresses across 5 prefixes while maintaining only 2 observed neighbours, a ratio characteristic of an access or eyeball network rather than a transit provider.
Notable
- All registrants in the RDAP data align with the announcer, consistently listing "Roanoke Connect" for prefixes including
108.161.192.0/20and158.51.180.0/22. - The inventory consists of five distinct IPv4 blocks, including a /20 and four /22s, with no IPv6 prefixes currently announced in the inventory.
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-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 5 prefixes · 8.19K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 5 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS19413- Registry name
- ROANOKE-CONNECT-ASN-1
- Registrant
- Roanoke Connect
- Abuse contact
- jwhitley@gofybe.com
- Registered
- 2020-01-13
- Last changed
- 2020-01-13
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Roanoke Connect
- Scope
- Regional
- Traffic ratio
- Mostly Inbound
- Peering policy
- Open
- Website
- https://www.roanokeelectric.com/roanoke-connect/
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, 24 with no ROA
- ROAs
- 0 authorising AS19413
- ASPA
- no ASPA record
- IRR
- 100% registered · 24 of 24 announcements
- Route objects
- 37 naming AS19413
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: 436 networks and 1,771 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