
This AS is not currently used to announce prefixes in the global routing table, nor is it used as a visible transit AS.
whois: 402332
IANA has recorded AS202683 as originally allocated by
/usr/bin/whois -h jwhois.apnic.netr "AS202683\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 'AS200537 - AS203022'
as-block: AS200537 - AS203022
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-04-08T13:28:00Z
last-modified: 2026-04-08T13:28:00Z
source: RIPE
% Information related to 'AS202683'
% Abuse contact for 'AS202683' is 'abuse@onehop-ix.ru'
aut-num: AS202683
as-name: ONEHOP-IX
org: ORG-LL556-RIPE
remarks:
remarks: ---------------------------------------------------------
remarks: This AS facilitates the ONEHOP-IX.RU Route Servers.
remarks:
remarks: All ASes participating in the Route Servers peering
remarks: are grouped into the AS-SET: AS202683:AS-ONEHOP
remarks:
remarks: Route Servers
remarks: ---------------------------------------------------------
remarks: rs1.onehop-ix.ru is 194.180.226.193 and 2001:7F8:100::226:100
remarks: rs2.onehop-ix.ru is 194.180.226.265 and 2001:7F8:100::226:200
remarks: ---------------------------------------------------------
remarks:
remarks: You may use communities to control outgoing information
remarks: via the route server.
remarks:
remarks: BGP Communities recognised for Route Servers:
remarks: Do not announce to a certain peer: 0:peer-as
remarks: Announce to a certain peer: 202683:peer-as
remarks: Do not announce to any peer: 0:202683
remarks: Announce to all peers: 202683:202683
remarks:
remarks: ---------------------------------------------------------
remarks:
remarks: Please visit https://onehop-ix.ru/route-server/
remarks: for more information on the onehop-ix.ru Route Servers
remarks: and details on the filtering options.
remarks:
admin-c: KES40-RIPE
admin-c: TN2777-RIPE
tech-c: TN2777-RIPE
sponsoring-org: ORG-CL261-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: MNT-TN
created: 2025-12-18T14:29:20Z
last-modified: 2025-12-19T12:58:17Z
source: RIPE
organisation: ORG-LL556-RIPE
org-name: Lightcom LLC
org-type: OTHER
address: 650055, Kuzbass, Kemerovo city, Lenina st, 33k2
country: RU
abuse-c: AR79331-RIPE
mnt-ref: MNT-TN
mnt-by: MNT-TN
created: 2025-11-03T19:29:03Z
last-modified: 2025-12-17T15:17:02Z
source: RIPE # Filtered
role: Network Operation Center
address: Russian Federation
phone: +7 499 348-25-10
remarks: ******************************************
remarks: Truenetwork NOC engineers available 24x7
remarks: ******************************************
remarks: Contact addresses:
remarks: Routing & peering: noc(at)truenetwork.ru
remarks: Spam & security: abuse(at)truenetwork.ru
remarks: mail: postmaster(at)truenetwork.ru
remarks: ddos reports: ddos(at)truenetwork.ru
remarks: ******************************************
nic-hdl: TN2777-RIPE
mnt-by: MNT-TN
created: 2014-06-30T08:26:40Z
last-modified: 2016-12-19T12:34:06Z
source: RIPE # Filtered
abuse-mailbox: abuse@truenetwork.ru
%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 (BUSA)