AS44892 - intersv.com
FOP Muhametdinov Oleg Angamovitch
AS44892 FOP Muhametdinov Oleg Angamovitch
as-block: AS42383 - AS45055 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: AS44892 as-name: FLY-AS org: ORG-FMOA1-RIPE import: from AS21379 action pref=100; accept ANY import: from AS43896 action pref=100; accept ANY export: to AS21379 announce AS44892 export: to AS43896 announce AS44892 admin-c: OM1179-RIPE tech-c: OM1179-RIPE status: ASSIGNED notify: email@example.com mnt-by: FLY1-MNT mnt-by: RIPE-NCC-END-MNT created: 2008-03-28T11:06:58Z last-modified: 2018-09-04T10:31:31Z source: RIPE sponsoring-org: ORG-DA29-RIPE organisation: ORG-FMOA1-RIPE org-name: FOP Muhametdinov Oleg Angamovitch org-type: OTHER address: Ukraine, 02028, Kiev, Raduzhna 55/202 e-mail: firstname.lastname@example.org abuse-c: AR30773-RIPE mnt-ref: FLY1-MNT mnt-by: FLY1-MNT created: 2008-03-21T02:32:17Z last-modified: 2014-11-17T22:49:44Z source: RIPE person: Oleg Muhametdinov address: Ukraine, 02218, Kiev, Raduzhna 55/202 phone: +380(44)406-50-11 e-mail: email@example.com nic-hdl: OM1179-RIPE mnt-by: FLY1-MNT created: 2008-03-21T02:23:27Z last-modified: 2008-03-25T11:55:08Z source: RIPE
IP Address Ranges
|126.96.36.199/23||FOP Muhametdinov Oleg Angamovitch||512|
There are no known IPv6 addresses belonging to this network
We don't currently have any network speed data for this network.
There are 2 domain names hosted across 2 IP addresses on this ASN. Checkout our API to access full domain hosting information.
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 AS44892 at robtex.