Skip to main content

AS47445

RIPN-RU-RND

RND RU services AS

Registry

Authoritative registration data

AS number
47445
Name
RIPN-RU-RND
Organisation
RND RU services AS
Country
—
RIR
RIPE
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 AS47445
193.232.139.0/24 IPv4 /24 not checked
193.232.236.0/24 IPv4 /24 not checked
195.209.12.0/24 IPv4 /24 not checked
2001:67c:1213::/48 IPv6 /48 RPKI valid
2001:6d0:ffb7::/48 IPv6 /48 not checked
2a0c:a9c7:236::/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 AS47445
Address families
MSK-IX Rostov-on-Don 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 AS47445 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS47445 in AS paths

Observed upstreams
Families
AS2854 ROSPRINT-AS 475 1,102
v4 v6
AS3316 RELARN 537 704
v4 v6
AS12389 ROSTELECOM-AS 259 617
v4 v6
AS20485 TRANSTELECOM 213 503
v4 v6
AS25091 IP-Max 5 25
v4 v6

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS47445 in AS paths

Observed downstreams
Families
AS43832 RIPN-NS5-RU-MSK 309 845
v4 v6
AS20144 IMRS 2 5
v4 v6
AS41740 NDNS 1 4
v4
AS42385 RIPN-RU 1 3
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS28917 Fiord-AS 4 11
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.