Skip to main content

AS398960

CRYOFLESH

Cryoflesh Inc

Registry

Authoritative registration data

AS number
398960
Name
CRYOFLESH
Organisation
Cryoflesh Inc
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

3

Total announced

6

Announced prefixes

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

Prefixes announced by AS398960
23.168.144.0/24 IPv4 /24 not checked
23.168.145.0/24 IPv4 /24 not checked
44.31.23.0/24 IPv4 /24 not checked
2602:808:4000::/48 IPv6 /48 not checked
2602:808:4002::/48 IPv6 /48 not checked
2602:808:4004::/48 IPv6 /48 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 AS398960
Address families
SIX Seattle (Jumbo): MTU 9000 1,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 1,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 AS398960 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS398960 in AS paths

Observed upstreams
Families
AS395823 DOOF 279 1,607
v4 v6
AS9002 RETN-AS 2 6
v4 v6
AS137409 GSLNETWORKS-AS-AP 2 6
v4 v6
AS18530 ISOMEDIA-1 1 3
v4 v6
AS394256 CLOUDSINGULARITY 1 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS398960 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 9
v4 v6
AS36236 NETACTUATE 1 3
v4 v6
AS49544 i3Dnet 1 3
v4 v6
AS35280 F5 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.