Skip to main content

AS25787

ROWE-NETWORKS

Rowe Wireless Networks LLC

Registry

Authoritative registration data

AS number
25787
Name
ROWE-NETWORKS
Organisation
Rowe Wireless Networks LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

1

Total announced

12

Announced prefixes

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

Prefixes announced by AS25787
142.249.140.0/22 IPv4 /22 not checked
162.217.20.0/22 IPv4 /22 not checked
205.137.252.0/22 IPv4 /22 not checked
142.249.140.0/24 IPv4 /24 not checked
142.249.141.0/24 IPv4 /24 not checked
142.249.142.0/24 IPv4 /24 not checked
162.217.20.0/24 IPv4 /24 not checked
162.217.21.0/24 IPv4 /24 not checked
162.217.22.0/24 IPv4 /24 not checked
162.217.23.0/24 IPv4 /24 not checked
74.123.208.0/24 IPv4 /24 not checked
2606:1640::/32 IPv6 /32 RPKI valid

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 AS25787
Address families
CMH-IX: Main 10,000 Mbps IPv4 · IPv6
Ohio IX: Ohio IX Public Peering LAN 10,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 AS25787 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS25787 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 458 3,240
v4 v6
AS32899 BRESCOBROADBAND 8 28
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS25787 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS20205 AMPLEX 1 10
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.