Skip to main content

AS394501

CRAVETECHNOLOGIESLTD

Crave Technologies Ltd.

Registry

Authoritative registration data

AS number
394501
Name
CRAVETECHNOLOGIESLTD
Organisation
Crave Technologies Ltd.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS394501
134.195.32.0/22 IPv4 /22 not checked
45.45.172.0/22 IPv4 /22 RPKI not found
134.195.32.0/24 IPv4 /24 RPKI not found
134.195.33.0/24 IPv4 /24 not checked
23.150.0.0/24 IPv4 /24 not checked
2605:1ec0::/32 IPv6 /32 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 AS394501
Address families
TorIX 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 AS394501 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS394501 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 140 633
v4 v6
AS1299 TWELVE99 122 378
v4 v6
AS7311 FRONTIER 5 13
v4 v6
AS394256 CLOUDSINGULARITY 1 6
v4 v6
AS20473 AS-VULTR 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS394501 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 22
v4 v6
AS22652 FIBRENOIRE-INTERNET 1 6
v4 v6
AS49544 i3Dnet 1 6
v4 v6
AS35280 F5 1 5
v4
AS1403 EBOX 1 2
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.