Skip to main content

AS20009

WADSNET

The City of Wadsworth

Registry

Authoritative registration data

AS number
20009
Name
WADSNET
Organisation
The City of Wadsworth
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS20009
67.23.144.0/20 IPv4 /20 not checked
104.192.176.0/22 IPv4 /22 not checked
142.54.18.0/23 IPv4 /23 not checked
67.23.144.0/24 IPv4 /24 not checked
2620:d5:2000::/48 IPv6 /48 RPKI not found

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS20009
Address families
Ohio IX: Ohio IX Public Peering LAN 100,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS20009 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS20009 in AS paths

Observed upstreams
Families
AS396238 FAIRLAWNGIG-NET 246 1,210
v4 v6
AS174 COGENT-174 102 421
v4 v6
AS19009 BLUEBIRDFIBER-1C 19 77
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS20009 in AS paths

Observed downstreams
Families
AS47046 WADSWORTH-CITYLINK 185 759
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS20205 AMPLEX 2 9
v4 v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.