Report for 39119

Name

CM-RU-AS, RU

AS Adjacency Report

In the context of this report "Upstream" indicates that there is an adjacent AS that lines between the BGP table collection point (in this case at AS2.0) and the specified AS. Similarly, "Downstream" refers to an adjacent AS that lies beyond the specified AS. This upstream / downstream categorisation is strictly a description relative topology, and should not be confused with provider / customer / peer inter-AS relationships.

39119 CM-RU-AS, RU

  Adjacency:     1  Upstream:     1  Downstream:     0
  Upstream Adjacent AS list
    AS47768         INTISTELECOM-AS, GB

Announced Prefixes

Rank  AS       Type    Originate Addr Space  (pfx)   Transit Addr space  (pfx)  Description
61788 AS39119        ORIGIN  Originate:        256 /24.00  Transit:          0 /0.00  CM-RU-AS, RU

Aggregation Suggestions

        Filter: Aggregates, Specifics

This report does not take into account conditions local to each origin AS in terms of policy or traffic engineering requirements, so this is an approximate guideline as to aggregation possibilities.

 Rank AS            AS Name                                      Current  Wthdw  Aggte  Annce Redctn       %
42302 AS39119       CM-RU-AS, RU                                       1      0      0      1      0   0.00%


  Prefix               AS Path                              Aggregation Suggestion
  195.66.84.0/24       4777 2497 174 47768 39119   

Whois Entry

whois: 402332

IANA has recorded AS39119 as originally allocated by 
/usr/bin/whois -h jwhois.apnic.netr "AS39119\n             % This is the RIPE Database query service.
             % The objects are in RPSL format.
             %
             % The RIPE Database is subject to Terms and Conditions.
             % See https://docs.db.ripe.net/terms-conditions.html
             
             % Note: this output has been filtered.
             
             % Information related to 'AS38912 - AS39599'
             
             as-block:       AS38912 - AS39599
             descr:          RIPE NCC ASN block
             remarks:        These AS Numbers are assigned to network operators in the RIPE NCC service region.
             mnt-by:         RIPE-NCC-HM-MNT
             created:        2023-08-29T07:47:54Z
             last-modified:  2023-08-29T07:47:54Z
             source:         RIPE
             
             % Information related to 'AS39119'
             
             % Abuse contact for 'AS39119' is 'ashot.shahbazian@coolmessages.net'
             
             aut-num:        AS39119
             as-name:        CM-RU-AS
             org:            ORG-CM11-RIPE
             import:         from AS12586 accept ANY
             import:         from AS47768 accept ANY
             export:         to AS12586 announce AS39119
             export:         to AS47768 announce AS39119
             admin-c:        AS44281-RIPE
             tech-c:         AS44281-RIPE
             status:         ASSIGNED
             mnt-by:         RIPE-NCC-END-MNT
             mnt-by:         MNT-RETNRU
             created:        2005-12-15T15:21:27Z
             last-modified:  2021-09-16T08:33:27Z
             source:         RIPE
             sponsoring-org: ORG-CA1293-RIPE
             
             organisation:   ORG-CM11-RIPE
             org-name:       Cool Messages Ltd.
             country:        RU
             org-type:       OTHER
             address:        Fortunatovskaya 12, Moscow 105187, Russian Federation
             abuse-c:        AC30293-RIPE
             mnt-ref:        MNT-RETNRU
             mnt-by:         MNT-RETNRU
             created:        2005-12-12T07:08:23Z
             last-modified:  2022-12-01T16:20:38Z
             source:         RIPE # Filtered
             
             %ERROR:201: access denied for 2401:2000:6660:0:0:0:0:13
             %
             % Queries from your IP address have passed the daily limit of controlled objects.
             % Access from your host has been temporarily denied.
             % For more information, see
             % https://docs.db.ripe.net/FAQ/#why-did-i-receive-an-error-201-access-denied
             
             % This query was served by the RIPE Database Query Service version 1.121.2 (SHETLAND)