Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS18118 (CITICNET-CN) announces 37 IPv4 and 0 IPv6 prefixes. 4 warnings
| AS page | AS18118 |
|---|---|
| Holder | CITICNET-CN - CITIC Networks Management Co.,Ltd. |
| Allocation | APNIC, China (CN), allocated 2002-03-12 |
| Prefixes (IPv4 / IPv6) | 37 / 0 |
| RPKI valid | 100% (37 / 37) |
| Upstreams and peers | 3 |
| Peering policy | Open |
What to fix
-
Warning
No IPv6 prefixes announced.
Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.
Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.
-
Warning
23 of 37 announced prefixes have no IRR route object: 120.47.223.0/24, 120.47.225.0/24, 219.72.156.0/24, 219.72.200.0/22, 120.47.96.0/19 (+18).
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS18118 in your RIR’s IRR database (or RADB).
route: 120.47.223.0/24 origin: AS18118 route: 120.47.225.0/24 origin: AS18118 route: 219.72.156.0/24 origin: AS18118
-
Warning
No IRR as-set is listed.
Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.
Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI No IPv6 prefixes announced.
- Pass: AS18118 announces 37 IPv4 and 0 IPv6 prefixes.
- Warning: No IPv6 prefixes announced.
- Pass: All 37 announced prefixes are RPKI valid.
- Warning: 23 of 37 announced prefixes have no IRR route object: 120.47.223.0/24, 120.47.225.0/24, 219.72.156.0/24, 219.72.200.0/22, 120.47.96.0/19 (+18).
- Info: 3 upstreams and peers, 0 downstream networks seen.
| Holder | CITICNET-CN - CITIC Networks Management Co.,Ltd. |
|---|---|
| IPv4 prefixes | 37 |
| IPv6 prefixes | 0 |
| RPKI | 37 valid |
| Without IRR route object | 23 |
| Downstream networks | 0 |
Upstreams and peers seen to the left 3
Announced prefixes 37
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.apnic.net.
- Pass: Found at rdap.apnic.net.
| Name | CITICNET-CN |
|---|---|
| Handle | AS18118 |
| Range | AS18118 |
| Country | CN |
| Status | active |
| Registered | 2008-09-04T06:40:32Z |
| Last changed | 2021-10-27T00:00:07Z |
| Abuse contact | wangjh1@citic.com |
| Registry (RIR) | APNIC |
|---|---|
| Country | China (CN) |
| Delegated on | 2002-03-12 |
| Status | Allocated |
| Delegated range | AS18118 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| administrative | Jing An | mof@citicnet.com |
| technical | Dongqing Han | handq@citicnet.com |
| abuse | IRT-CITICNET-CN-CN | wangjh1@citic.com |
Source: https://rdap.apnic.net/autnum/18118. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB No IRR as-set is listed.
- Pass: AS18118 is in PeeringDB as CITIC Networks Management.
- Info: Peering policy: Open.
- Info: Present at 1 internet exchanges with 1 ports (10G in total).
- Warning: No IRR as-set is listed.
- Warning: No public NOC, policy or technical contact.
| Network | CITIC Networks Management (中信数科) |
|---|---|
| AS number | AS18118 |
| Type | Cable/DSL/ISP, Asia Pacific |
| Website | https://www.citicnetworks.com/ |
| Traffic | Not Disclosed |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Required |
| Last updated | 2026-04-09 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup