Skip to main content

AS212154

SARUNETWORK-AS

Saru Network

Registry

Authoritative registration data

AS number
212154
Name
SARUNETWORK-AS
Organisation
Saru Network
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

3

Total announced

3

Announced prefixes

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

Prefixes announced by AS212154
2a05:dfc3:fd0f::/48 IPv6 /48 not checked
2a0e:8f02:f047::/48 IPv6 /48 not checked
2a0e:b107:1c0f::/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 AS212154
Address families
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv6
Poema IX 100 Mbps 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 AS212154 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS212154 in AS paths

Observed upstreams
Families
AS212895 ROUTE64_ORG 271 980
v6
AS34872 Servperso_Systems 56 82
v6
AS25091 IP-Max 3 21
v6
AS8298 IPNG 2 6
v6
AS209533 BGPTunnel 2 4
v6
AS401753 1 3
v6
AS34927 iFog-GmbH 2 2
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS212154 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS56662 1 3
v6
AS199854 1 3
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.