Skip to main content

AS21709

IMPLEX-NET

Implex.net, Inc.

Registry

Authoritative registration data

AS number
21709
Name
IMPLEX-NET
Organisation
Implex.net, Inc.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS21709
173.225.128.0/20 IPv4 /20 not checked
69.54.32.0/20 IPv4 /20 not checked

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 AS21709
Address families
IX-Denver: IX-Denver Fabric 10,000 Mbps IPv4 · IPv6
KCIX 10,000 Mbps IPv4 · IPv6
MICE: Shared Peering 10,000 Mbps IPv4 · IPv6
QCIX: Main 10,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 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 AS21709 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS21709 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 229 648
v4
AS174 COGENT-174 36 94
v4
AS394256 CLOUDSINGULARITY 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS21709 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 6
v4
AS49544 i3Dnet 1 4
v4
AS1003 ANDREWNET 1 2
v4
AS1828 UNITAS 1 2
v4
AS9002 RETN-AS 1 2
v4
AS35280 F5 1 2
v4
AS36236 NETACTUATE 1 2
v4
AS394414 AS394414 1 2
v4

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.