Skip to main content

AS34456

RIALCOM-AS

****************************

Registry

Authoritative registration data

AS number
34456
Name
RIALCOM-AS
Organisation
****************************
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

36

IPv6 prefixes

0

Total announced

36

Announced prefixes

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

Prefixes announced by AS34456
37.1.0.0/18 IPv4 /18 RPKI not found
37.1.0.0/19 IPv4 /19 not checked
37.1.32.0/19 IPv4 /19 not checked
62.176.0.0/19 IPv4 /19 not checked
46.249.0.0/20 IPv4 /20 not checked
62.176.0.0/20 IPv4 /20 not checked
62.176.16.0/20 IPv4 /20 not checked
80.71.240.0/20 IPv4 /20 not checked
83.220.176.0/20 IPv4 /20 RPKI not found
164.215.48.0/21 IPv4 /21 not checked
213.159.216.0/21 IPv4 /21 RPKI not found
46.249.0.0/21 IPv4 /21 RPKI not found
46.249.8.0/21 IPv4 /21 not checked
80.71.240.0/21 IPv4 /21 not checked
80.71.248.0/21 IPv4 /21 RPKI not found
83.220.176.0/21 IPv4 /21 not checked
83.220.184.0/21 IPv4 /21 not checked
164.215.48.0/22 IPv4 /22 RPKI not found
164.215.52.0/22 IPv4 /22 not checked
185.52.68.0/22 IPv4 /22 RPKI not found
185.68.116.0/22 IPv4 /22 RPKI not found
185.69.124.0/22 IPv4 /22 RPKI not found
185.7.152.0/22 IPv4 /22 RPKI not found
185.72.188.0/22 IPv4 /22 not checked
213.159.216.0/22 IPv4 /22 RPKI not found
213.159.220.0/22 IPv4 /22 not checked
185.52.68.0/23 IPv4 /23 RPKI not found
185.52.70.0/23 IPv4 /23 not checked
185.68.116.0/23 IPv4 /23 RPKI not found
185.68.118.0/23 IPv4 /23 RPKI not found
185.69.124.0/23 IPv4 /23 RPKI not found
185.69.126.0/23 IPv4 /23 RPKI not found
185.7.152.0/23 IPv4 /23 not checked
185.7.154.0/23 IPv4 /23 RPKI not found
185.72.188.0/23 IPv4 /23 RPKI not found
185.72.190.0/23 IPv4 /23 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 AS34456
Address families
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network 20,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 AS34456 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS34456 in AS paths

Observed upstreams
Families
AS25091 IP-Max 23 486
v4
AS20764 RASCOM-AS 12 124
v4
AS49434 FBWNETWORKS 7 75
v4
AS41327 FIBERTELECOM-AS 6 74
v4
AS13194 BITE 3 37
v4
AS9198 KAZTELECOM-AS 3 19
v4
AS43727 KVANT-TELECOM 1 19
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS34456 in AS paths

Observed downstreams
Families
AS48321 RialcomOOO-AS 26 30
v4
AS196667 ApeksSecurity-AS 8 10
v4
AS50009 QUARTZ-AS 2 5
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS34927 iFog-GmbH 3 74
v4
AS37721 ORG-VTS1-AFRINIC 4 38
v4
AS28910 INTAL-ASN 3 37
v4
AS36236 NETACTUATE 3 37
v4
AS41722 MIRAN-AS 3 37
v4
AS35598 INETCOM 2 37
v4
AS49673 TRUENETWORK 2 31
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.