AS39585 - radiocon.ru
AS39585 Radio-Continental Ltd.
as-block: AS38912 - AS39935 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: 2018-11-22T15:27:34Z last-modified: 2018-11-22T15:27:34Z source: RIPE aut-num: AS39585 as-name: RADIO-CONTINENTAL-AS org: ORG-RL112-RIPE import: from AS47271 action pref=100; accept ANY import: from AS29196 accept ANY export: to AS47271 announce AS39585 export: to AS29196 announce AS39585 admin-c: KS3022-RIPE tech-c: KS3022-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: MNT-RADIO-CONTINENTAL created: 2011-12-27T08:15:47Z last-modified: 2019-03-18T12:30:53Z source: RIPE notify: email@example.com sponsoring-org: ORG-ETL23-RIPE organisation: ORG-RL112-RIPE org-name: Radio-Continental Ltd. org-type: OTHER address: Radio-Continental Ltd. address: Ordzhonikidze, 58 A address: 454000 CHELYABINSK address: RUSSIAN FEDERATION fax-no: +73512650189 e-mail: firstname.lastname@example.org abuse-c: AR21490-RIPE mnt-ref: MNT-RADIO-CONTINENTAL mnt-by: MNT-RADIO-CONTINENTAL created: 2011-11-30T10:44:26Z last-modified: 2014-07-22T12:26:20Z source: RIPE person: Konstantin Sereda address: Radio-Continental Ltd. address: 58 A Ordjonikidze address: Chelyabinsk address: 454000, Russia phone: +7-351-7299903 e-mail: email@example.com nic-hdl: KS3022-RIPE mnt-by: MNT-RADIO-CONTINENTAL created: 2006-09-04T13:21:15Z last-modified: 2012-02-10T03:20:47Z source: RIPE
IP Address Ranges
There are no known IPv6 addresses belonging to this network
We don't currently have any network speed data for this network.
There are no domains currently hosted on this ASN.
There are 2 peers for this ASN.
There are 2 upstreams for this ASN.
There are no downstreams for this ASN.
Autonomous System Numbers (ASNs) are assigned to entities such as Internet Service Providers and other large organizations that control blocks of IP addresses. This network page, and the organization field that's shown on the main IP address information page and also returned in the geolocation API are based on the ASN.
The ASN details will often correspond to the IP address owner, but for smaller organizations it may be that organization's parent, or their ISP.
Find out more about AS39585 at robtex.