Skip to main content

AS29388

ASN-BESTCOM

Moscow, Russia

Registry

Authoritative registration data

AS number
29388
Name
ASN-BESTCOM
Organisation
Moscow, Russia
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS29388
217.72.144.0/20 IPv4 /20 not checked
217.72.154.0/23 IPv4 /23 not checked
217.72.150.0/24 IPv4 /24 not checked
2a02:5800::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS29388 in AS paths

Observed upstreams
Families
AS8732 COMCOR-AS 326 925
v4 v6
AS12389 150 186
v4
AS6939 HURRICANE 83 143
v4 v6
AS3216 SOVAM-AS 50 74
v4
AS25091 IP-Max 5 32
v4 v6
AS41327 FIBERTELECOM-AS 2 6
v4 v6
AS209141 CMI-Russia 1 2
v4
AS9198 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS29388 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 12
v4 v6
AS28917 1 5
v4 v6
AS28910 1 4
v4 v6
AS36236 NETACTUATE 1 4
v4 v6
AS41722 1 4
v4 v6
AS29049 1 3
v4
AS35598 1 3
v4
AS49673 TRUENETWORK 1 3
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.