Skip to main content

AS21632

CYBERNET1

Cybernet1

Registry

Authoritative registration data

AS number
21632
Name
CYBERNET1
Organisation
Cybernet1
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

0

Total announced

12

Announced prefixes

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

Prefixes announced by AS21632
108.174.112.0/20 IPv4 /20 not checked
216.166.148.0/24 IPv4 /24 not checked
66.62.113.0/24 IPv4 /24 not checked
66.62.121.0/24 IPv4 /24 not checked
66.62.122.0/24 IPv4 /24 not checked
66.62.123.0/24 IPv4 /24 not checked
66.62.124.0/24 IPv4 /24 not checked
66.62.126.0/24 IPv4 /24 not checked
66.62.166.0/24 IPv4 /24 not checked
66.62.89.0/24 IPv4 /24 not checked
66.62.93.0/24 IPv4 /24 not checked
66.62.95.0/24 IPv4 /24 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 AS21632
Address families
SIX Seattle (Jumbo): MTU 9000 100,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 110,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 AS21632 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS21632 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 265 4,437
v4
AS394256 CLOUDSINGULARITY 1 12
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS21632 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 36
v4
AS49544 i3Dnet 1 24
v4
AS9002 RETN-AS 1 12
v4
AS34927 iFog-GmbH 1 12
v4
AS35280 F5 1 12
v4
AS36236 NETACTUATE 1 12
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.