Skip to main content

AS394745

LH-AS-1

Lunanode Hosting Inc.

Registry

Authoritative registration data

AS number
394745
Name
LH-AS-1
Organisation
Lunanode Hosting Inc.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS394745
170.75.160.0/20 IPv4 /20 RPKI valid
172.81.176.0/21 IPv4 /21 RPKI valid
2602:ffb6::/36 IPv6 /36 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 AS394745
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 AS394745 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS394745 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 53 81
v4 v6
AS20473 AS-VULTR 1 1
v6
AS394256 CLOUDSINGULARITY 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS394745 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 33
v4 v6
AS49544 i3Dnet 1 6
v4 v6
AS1828 UNITAS 1 3
v4 v6
AS22652 FIBRENOIRE-INTERNET 1 3
v4 v6
AS835 GOCODEIT-EDGE 1 2
v4
AS1403 EBOX 1 2
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.