Registration
IPv4 Prefixes
30 prefixes · 12,032 addresses Routing data as of 2026-10-17 08:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 110.166.64.0/20 | 110.166.64.0 – 110.166.79.255 | 4,096 |
| 110.167.163.0/24 | 110.167.163.0 – 110.167.163.255 | 256 |
| 110.167.164.0/24 | 110.167.164.0 – 110.167.164.255 | 256 |
| 110.167.255.0/24 | 110.167.255.0 – 110.167.255.255 | 256 |
| 118.213.88.0/24 | 118.213.88.0 – 118.213.88.255 | 256 |
| 118.213.92.0/24 | 118.213.92.0 – 118.213.92.255 | 256 |
| 118.213.93.0/24 | 118.213.93.0 – 118.213.93.255 | 256 |
| 118.213.141.0/24 | 118.213.141.0 – 118.213.141.255 | 256 |
| 118.213.220.0/24 | 118.213.220.0 – 118.213.220.255 | 256 |
| 125.72.18.0/23 | 125.72.18.0 – 125.72.19.255 | 512 |
| 125.72.124.0/24 | 125.72.124.0 – 125.72.124.255 | 256 |
| 125.72.126.0/24 | 125.72.126.0 – 125.72.126.255 | 256 |
| 125.72.138.0/24 | 125.72.138.0 – 125.72.138.255 | 256 |
| 125.72.141.0/24 | 125.72.141.0 – 125.72.141.255 | 256 |
| 125.72.143.0/24 | 125.72.143.0 – 125.72.143.255 | 256 |
| 125.72.144.0/24 | 125.72.144.0 – 125.72.144.255 | 256 |
| 125.72.145.0/24 | 125.72.145.0 – 125.72.145.255 | 256 |
| 125.72.146.0/24 | 125.72.146.0 – 125.72.146.255 | 256 |
| 125.72.147.0/24 | 125.72.147.0 – 125.72.147.255 | 256 |
| 220.154.116.0/24 | 220.154.116.0 – 220.154.116.255 | 256 |
| 220.154.117.0/24 | 220.154.117.0 – 220.154.117.255 | 256 |
| 220.167.142.0/23 | 220.167.142.0 – 220.167.143.255 | 512 |
| 220.167.180.0/24 | 220.167.180.0 – 220.167.180.255 | 256 |
| 220.167.181.0/24 | 220.167.181.0 – 220.167.181.255 | 256 |
| 220.167.182.0/24 | 220.167.182.0 – 220.167.182.255 | 256 |
| 223.221.10.0/24 | 223.221.10.0 – 223.221.10.255 | 256 |
| 223.221.162.0/24 | 223.221.162.0 – 223.221.162.255 | 256 |
| 223.221.177.0/24 | 223.221.177.0 – 223.221.177.255 | 256 |
| 223.221.179.0/24 | 223.221.179.0 – 223.221.179.255 | 256 |
| 223.221.216.0/24 | 223.221.216.0 – 223.221.216.255 | 256 |
IPv6 Prefixes
2 prefixes · 2 × /48 Routing data as of 2026-10-17 08:00 UTC
| Prefix | Addresses |
|---|---|
| 240e:981:7101:: | 280 |
| 240e:981:7102:: | 280 |
BGP Neighbours
1 unique neighbour · 1 upstream/peer · 0 downstream. A neighbour can be seen on more than one side. Rows are ordered by AS paths: the number of BGP paths seen by RIPE RIS that contain the adjacency. Sightings count each IPv4/IPv6 route with the adjacency once per RIS peer that sees it (routes × peers), so they show how widely it is seen, not how many distinct routes it carries. Networks seen to the left of this AS in BGP paths, toward the route collectors — typically its transit providers (upstreams) and peers. Upstream & peer side (1)
AS Name AS paths IPv4 sightings IPv6 sightings AS140061 CHINANET-Qinghai-AS-AP - Qinghai Telecom 434 9,449 664
Raw RDAP Response
{
"rdapConformance": [
"history_version_0",
"nro_rdap_profile_0",
"nro_rdap_profile_asn_hierarchical_0",
"cidr0",
"rdap_level_0"
],
"notices": [
{
"title": "Source",
"description": [
"Objects returned came from source",
"APNIC"
]
},
{
"title": "Terms and Conditions",
"description": [
"This is the APNIC WHOIS Database query service. The objects are in RDAP format."
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/59223",
"rel": "terms-of-service",
"href": "http://www.apnic.net/db/dbcopyright.html",
"type": "text/html"
}
]
},
{
"title": "Whois Inaccuracy Reporting",
"description": [
"If you see inaccuracies in the results, please visit: "
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/59223",
"rel": "inaccuracy-report",
"href": "https://www.apnic.net/manage-ip/using-whois/abuse-and-spamming/invalid-contact-form",
"type": "text/html"
}
]
}
],
"country": "CN",
"name": "CT-Qinghai-IDC",
"status": [
"active"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2013-11-05T00:14:02Z"
},
{
"eventAction": "last changed",
"eventDate": "2024-04-08T06:06:28Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/59223",
"rel": "self",
"href": "https://rdap.apnic.net/autnum/59223",
"type": "application/rdap+json"
}
],
"remarks": [
{
"description": [
"CHINANET Qinghai province IDC network"
],
"title": "description"
},
{
"description": [
"CHINANET Qinghai province IDC network"
],
"title": "remarks"
}
],
"entities": [
{
"roles": [
"abuse"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2010-11-15T00:31:55Z"
},
{
"eventAction": "last changed",
"eventDate": "2026-05-21T01:31:36Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/59223",
"rel": "self",
"href": "https://rdap.apnic.net/entity/IRT-CHINANET-CN",
"type": "application/rdap+json"
}
],
"remarks": [
{
"description": [
"[email protected] was validated on 2026-05-21"
],
"title": "remarks"
}
],
"handle": "IRT-CHINANET-CN",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"IRT-CHINANET-CN"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "No.31 ,jingrong street,beijing\n100032"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"email",
{},
"text",
"[email protected]"
],
[
"email",
{
"pref": "1"
},
"text",
"[email protected]"
]
]
]
},
{
"roles": [
"technical",
"administrative"
],
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T07:48:38Z"
},
{
"eventAction": "last changed",
"eventDate": "2008-09-04T07:48:38Z"
}
],
"links": [
{
"value": "https://rdap.apnic.net/autnum/59223",
"rel": "self",
"href": "https://rdap.apnic.net/entity/GF298-AP",
"type": "application/rdap+json"
}
],
"handle": "GF298-AP",
"objectClassName": "entity",
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"REDACTED"
],
[
"kind",
{},
"text",
"individual"
]
]
]
}
],
"handle": "AS59223",
"startAutnum": 59223,
"endAutnum": 59223,
"objectClassName": "autnum",
"port43": "whois.apnic.net"
} Contact details of private individuals are redacted.