Skip to content
thenetworkery

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.

IP address, prefix or AS number

AS18118 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS18118"
JSON Docs

Warning: AS18118 (CITICNET-CN) announces 37 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS18118
HolderCITICNET-CN - CITIC Networks Management Co.,Ltd.
AllocationAPNIC, China (CN), allocated 2002-03-12
Prefixes (IPv4 / IPv6)37 / 0
RPKI valid100% (37 / 37)
Upstreams and peers3
Peering policyOpen

What to fix

  1. 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.

    Open in ASN & BGP prefix lookup

  2. 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

    Open in ASN & BGP prefix lookup

  3. 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.

    Open in PeeringDB lookup

  4. 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.

    Open in PeeringDB lookup

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.
HolderCITICNET-CN - CITIC Networks Management Co.,Ltd.
IPv4 prefixes37
IPv6 prefixes0
RPKI37 valid
Without IRR route object23
Downstream networks0

Upstreams and peers seen to the left 3

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameCITICNET-CN
HandleAS18118
RangeAS18118
CountryCN
Statusactive
Registered2008-09-04T06:40:32Z
Last changed2021-10-27T00:00:07Z
Abuse contactwangjh1@citic.com
Allocation
Registry (RIR)APNIC
CountryChina (CN)
Delegated on2002-03-12
StatusAllocated
Delegated rangeAS18118

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
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 lookup
PeeringDB 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.
NetworkCITIC Networks Management (中信数科)
AS numberAS18118
TypeCable/DSL/ISP, Asia Pacific
Websitehttps://www.citicnetworks.com/
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsRequired
Last updated2026-04-09

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup