Autonomous system
AS13576 SDNW-13576
Residential ARIN Cable/DSL/ISP
Summary
SDN Communications
isp telecom transit
A cooperative carrying its member telcos' own blocks, with customer account numbers and the word unassigned published in reverse DNS.
What it's used for
- A regional carrier owned by independent telephone companies. 54,272 addresses across 109 IPv4 prefixes, three IPv6 prefixes, and fifty-eight observed BGP neighbours.
Notable
- Announced blocks are registered to several separate companies: a tribal telephone authority, two cooperatives, and a telecommunications company that also appears under a fibre trading name.
- The carrier's own registrant strings append two internal teams after semicolons, and the order of those two teams differs between records.
- Netnames such as
SDN-66-115-192-0name the parent range rather than the block being registered. - One sampled name is
cust.170935.sxflsdch38R.sdnet.net, anotherGE2-6.520.SXFLSDCH17R.cust.sdnet.net. - One answers as
254.170.128.66.unassigned.sdncommunications.com.
Interesting
- A six-digit number in the customer label is an account or circuit reference, readable by anyone who asks the address what it is called. The other form gives a router port and a segment number instead, which is the same disclosure aimed at a different audience.
- Publishing
unassignedas a label is honest and useful internally, and it tells a scanner exactly which addresses nobody is watching. - Member-owned blocks announced under one number is the cooperative model in the routing table: ownership stays with each telephone company, reachability is pooled.
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 2 exchanges in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Midwest Internet Cooperative Exchange | Minneapolis, United States | 206.108.255.49 |
| Interconnection eXchange Denver | Denver, United States | 206.53.175.35 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 105 prefixes · 53.25K addresses IPv6 3 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 108 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS13576- Registry name
- SDNW-13576
- Registrant
- SDN Communications
- Abuse contact
- arin.abuse@sdncommunications.com
- Registered
- 1999-07-08
- Last changed
- 2026-02-04
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- South Dakota Network dba SDN Communications
- Also known as
- sdnet.net
- Network type
- Cable/DSL/ISP
- Scope
- Regional
- Traffic ratio
- Mostly Inbound
- Peering policy
- Selective
- IRR as-set
AS-13576-SDN-PEERS- Present at
- 3 exchanges
- Facilities
- 11 facilities
- Website
- http://www.sdncommunications.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
- 83% valid · 59 valid, 12 with no ROA
- ROAs
- 74 authorising AS13576
- ASPA
- 7 declared providers
- IRR
- 99% registered · 70 of 71 announcements
- Route objects
- 99 naming AS13576
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: 431 networks and 1,768 prefixes, as published 2026-10-12. 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