Report for 49662

Name

LOHIKA-AS, 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.

49662 LOHIKA-AS, UA

  Adjacency:     1  Upstream:     1  Downstream:     0
  Upstream Adjacent AS list
    AS44600         GT-AS, UA

Announced Prefixes

Rank  AS       Type    Originate Addr Space  (pfx)   Transit Addr space  (pfx)  Description
63600 AS49662        ORIGIN  Originate:        256 /24.00  Transit:          0 /0.00  LOHIKA-AS, 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       %
46883 AS49662       LOHIKA-AS, UA                                      1      0      0      1      0   0.00%


  Prefix               AS Path                              Aggregation Suggestion
  91.213.92.0/24       4777 6939 44600 49662   

Whois Entry

whois: 402332

IANA has recorded AS49662 as originally allocated by 
/usr/bin/whois -h jwhois.apnic.netr "AS49662\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 'AS49386 - AS49866'
             
             as-block:       AS49386 - AS49866
             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:        2026-02-24T07:14:53Z
             last-modified:  2026-02-24T07:14:53Z
             source:         RIPE
             
             % Information related to 'AS49662'
             
             % Abuse contact for 'AS49662' is 'abuse@unc.kiev.ua'
             
             aut-num:        AS49662
             as-name:        Lohika-AS
             org:            ORG-CUL22-RIPE
             import:         from AS1820 accept ANY
             import:         from AS3326 accept ANY
             export:         to AS1820 announce AS49662
             export:         to AS3326 announce AS49662
             default:        to AS3326
             sponsoring-org: ORG-LMK5-RIPE
             admin-c:        MP40831-RIPE
             tech-c:         MP40831-RIPE
             status:         ASSIGNED
             mnt-by:         RIPE-NCC-END-MNT
             mnt-by:         Capgemini-UA-MNT
             created:        2009-07-27T09:29:47Z
             last-modified:  2026-02-02T15:03:38Z
             source:         RIPE # Filtered
             
             organisation:   ORG-CUL22-RIPE
             org-name:       CAPGEMINI UKRAINE LLC
             country:        UA
             org-type:       OTHER
             address:        50 Sem'yi Prakhovykh, 01033, Kyiv, Ukraine
             abuse-c:        AR65759-RIPE
             mnt-ref:        Capgemini-UA-MNT
             created:        2026-01-21T08:28:29Z
             last-modified:  2026-02-02T15:03:38Z
             source:         RIPE # Filtered
             mnt-by:         Capgemini-UA-MNT
             
             %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 (ABERDEEN)