Report for 59461

Name

ASBERLAYN, UA

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.

59461 ASBERLAYN, UA

  Adjacency:     1  Upstream:     1  Downstream:     0
  Upstream Adjacent AS list
    AS43418         ANTIDOT, UA

Announced Prefixes

Rank  AS       Type    Originate Addr Space  (pfx)   Transit Addr space  (pfx)  Description
37548 AS59461        ORIGIN  Originate:       1024 /22.00  Transit:          0 /0.00  ASBERLAYN, UA

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       %
50897 AS59461       ASBERLAYN, UA                                      1      0      0      1      0   0.00%


  Prefix               AS Path                              Aggregation Suggestion
  91.240.140.0/22      4777 2497 174 35320 43418 59461   

Whois Entry

whois: 402332

IANA has recorded AS59461 as originally allocated by 
/usr/bin/whois -h jwhois.apnic.netr "AS59461\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 'AS59392 - AS60437'
             
             as-block:       AS59392 - AS60437
             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:        2024-09-03T13:31:09Z
             last-modified:  2024-09-03T13:31:09Z
             source:         RIPE
             
             % Information related to 'AS59461'
             
             % Abuse contact for 'AS59461' is 'abuse@berline.kiev.ua'
             
             aut-num:        AS59461
             as-name:        ASBERLAYN
             org:            ORG-BERL3-RIPE
             import:         from AS43418 action pref=120; accept ANY
             export:         to AS43418 announce AS59461
             import:         from AS34251 action pref=120; accept ANY
             export:         to AS34251 announce AS59461
             admin-c:        ALEX23-RIPE
             tech-c:         ALEX23-RIPE
             status:         ASSIGNED
             mnt-by:         RIPE-NCC-END-MNT
             mnt-by:         BERLAYN-MNT
             created:        2012-07-17T13:04:06Z
             last-modified:  2018-09-04T11:14:06Z
             source:         RIPE
             sponsoring-org: ORG-Vs35-RIPE
             
             organisation:   ORG-BERL3-RIPE
             org-name:       TOV "BERLAYN"
             country:        UA
             org-type:       OTHER
             address:        Ukraine, Kiev, 02098, st. P.Tychiny, 18V
             abuse-c:        AR30513-RIPE
             mnt-ref:        BERLAYN-MNT
             mnt-by:         BERLAYN-MNT
             created:        2012-06-27T16:11:08Z
             last-modified:  2022-12-01T16:17:33Z
             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)