Skip to main content

AS213461

NorthernLightsCloud

Registry

Authoritative registration data

AS number
213461
Name
NorthernLightsCloud
Organisation
NorthernLightsCloud
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS213461
185.162.235.0/24 IPv4 /24 RPKI valid
2a10:ccc1:1338::/47 IPv6 /47 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 AS213461
Address families
GNM-IX 10,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 5,000 Mbps IPv4

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 AS213461 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS213461 in AS paths

Observed upstreams
Families
AS200993 NyaCore 137 166
v4
AS6939 HURRICANE 54 65
v6
AS8218 NEO-ASN 3 4
v6
AS47692 NESSUS 2 4
v6
AS25091 IP-Max 3 3
v6
AS50629 LWLCOM 2 2
v6
AS33891 CORE-BACKBONE 1 1
v6
AS39351 ESAB-AS 1 1
v6
AS56655 GIGAHOST 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS213461 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 5
v6
AS37721 ORG-VTS1-AFRINIC 1 1
v6
AS48919 UA-CITY-AS 1 1
v6
AS199524 GCORE 1 1
v6
AS205112 PHILUNET 1 1
v6
AS208972 1 1
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.