AS41762 - sevcity.net
PE Logvinov Vladimir Vladimirovich
AS41762 PE Logvinov Vladimir Vladimirovich
as-block: AS40960 - AS42381 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: AS41762 as-name: SEVNET org: ORG-STR3-RIPE import: from AS6703 accept ANY import: from AS35381 accept ANY export: to AS6703 announce AS-STRELKA export: to AS35381 announce AS41762 admin-c: SS4096-RIPE tech-c: SS4096-RIPE status: ASSIGNED notify: email@example.com mnt-by: LVV51-MNT mnt-by: RIPE-NCC-END-MNT created: 2006-10-20T12:30:26Z last-modified: 2018-09-04T10:19:28Z source: RIPE sponsoring-org: ORG-LKP1-RIPE organisation: ORG-STR3-RIPE org-name: PE Logvinov Vladimir Vladimirovich descr: PE Logvinov Vladimir Vladimirovich admin-c: SS4096-RIPE tech-c: SS4096-RIPE org-type: OTHER address: Sevastopol, Ukraine e-mail: firstname.lastname@example.org abuse-c: AR26063-RIPE mnt-ref: LVV51-MNT mnt-by: LVV51-MNT created: 2006-10-16T10:01:21Z last-modified: 2014-11-17T21:46:35Z source: RIPE person: Sergey Bezmaternykh address: SEVNET ISP address: Sevastopol, Ukraine mnt-by: AS35381-MNT phone: +3 8050 4971438 nic-hdl: SS4096-RIPE notify: email@example.com e-mail: firstname.lastname@example.org created: 2008-01-14T11:11:29Z last-modified: 2010-06-09T12:37:46Z source: RIPE
IP Address Ranges
|220.127.116.11/24||PE Logvinov Vladimir Vladimirovich||256|
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 is 1 peer for this ASN.
There is 1 upstream 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 AS41762 at robtex.