as-block: AS40960 - 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: 2015-12-10T09:19:56Z last-modified: 2015-12-10T09:19:56Z source: RIPE aut-num: AS44429 as-name: MXTEL-AS org: ORG-MTL14-RIPE import: from AS12695 accept ANY import: from AS5537 accept ANY import: from AS49583 accept AS49583 import: from AS44020 accept AS44020 export: to AS12695 announce AS-MXTEL export: to AS5537 announce AS-MXTEL export: to AS49583 announce ANY export: to AS44020 announce ANY admin-c: MTN30-RIPE tech-c: MTN30-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-routes: DN-MNT mnt-routes: RIPE-DB-MNT mnt-routes: ROSNIIROS-MNT mnt-by: RIPE-DB-MNT created: 2008-01-18T14:24:19Z last-modified: 2016-11-25T12:47:18Z source: RIPE sponsoring-org: ORG-ATS13-RIPE organisation: ORG-MTL14-RIPE org-name: MX Telecom LTD org-type: OTHER address: Moscow, Russia address: VerhnelihoborskajÃ st, d.8 e-mail: email@example.com admin-c: AM4275-RIPE tech-c: AM4275-RIPE abuse-c: MTN30-RIPE mnt-ref: RIPE-DB-MNT mnt-by: RIPE-DB-MNT created: 2008-01-16T12:11:12Z last-modified: 2016-11-25T13:53:33Z source: RIPE role: MX Telecom NOC address: 8 Verhnelihoborskaya, Moscow, Russia e-mail: firstname.lastname@example.org admin-c: VP12861-RIPE tech-c: VP12861-RIPE nic-hdl: MTN30-RIPE abuse-mailbox: email@example.com mnt-by: RIPE-DB-MNT created: 2015-07-14T17:32:33Z last-modified: 2016-11-25T14:20:31Z source: RIPE
IP Address Ranges
We don't currently have any network speed data for this network.
There are 7 domain names hosted across 5 IP addresses on this ASN. Checkout our API to access full domain hosting information.
|IP Address||Domain||Domains on this IP|
There is 1 peer 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 AS44429 at robtex.