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

AS4847 ·

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

Problem: AS4847 (CNIX-AP) announces 876 IPv4 and 11 IPv6 prefixes. 1 problem · 4 warnings

AS pageAS4847
HolderCNIX-AP - China Networks Inter-Exchange
AllocationAPNIC, China (CN), allocated 1996-09-10
Prefixes (IPv4 / IPv6)876 / 11
RPKI valid83% (732 / 887)
Upstreams and peers2

What to fix

  1. Problem

    12 of 887 announced prefixes are RPKI invalid: 123.58.232.0/22, 123.58.232.0/24, 123.58.233.0/24, 123.58.234.0/24, 123.58.235.0/24 (+7).

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    9 of 887 announced prefixes have no ROA (RPKI not found): 49.221.26.0/23, 49.221.64.0/19, 49.221.128.0/19, 60.247.0.0/17, 60.247.0.0/19 (+4).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS4847 and a max length equal to the prefix length:

    49.221.26.0/23 AS4847 max-length /23
    49.221.64.0/19 AS4847 max-length /19
    49.221.128.0/19 AS4847 max-length /19
    60.247.0.0/17 AS4847 max-length /17
    60.247.0.0/19 AS4847 max-length /19
    60.247.28.0/24 AS4847 max-length /24
    60.247.32.0/19 AS4847 max-length /19
    60.247.45.0/24 AS4847 max-length /24
    60.247.64.0/19 AS4847 max-length /19

    Open in RPKI / ROA validator Guide

  3. Warning

    143 of 887 announced prefixes have no IRR route object: 118.194.134.0/23, 45.124.21.0/24, 118.187.56.0/24, 218.240.7.0/24, 101.96.132.0/23 (+138).

    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 AS4847 in your RIR’s IRR database (or RADB).

    route: 118.194.134.0/23
    origin: AS4847
    
    route: 45.124.21.0/24
    origin: AS4847
    
    route: 118.187.56.0/24
    origin: AS4847

    Open in ASN & BGP prefix lookup

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

  5. 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 12 of 887 announced prefixes are RPKI invalid: 123.58.232.0/22, 123.58.232.0/24, 123.58.233.0/24, 123.58.234.0/24, 123.58.235.0/24 (+7).
  • Pass: AS4847 announces 876 IPv4 and 11 IPv6 prefixes.
  • Problem: 12 of 887 announced prefixes are RPKI invalid: 123.58.232.0/22, 123.58.232.0/24, 123.58.233.0/24, 123.58.234.0/24, 123.58.235.0/24 (+7).
  • Warning: 9 of 887 announced prefixes have no ROA (RPKI not found): 49.221.26.0/23, 49.221.64.0/19, 49.221.128.0/19, 60.247.0.0/17, 60.247.0.0/19 (+4).
  • Info: 732 of 887 announced prefixes are RPKI valid.
  • Info: The RPKI state of 134 prefixes was not looked up (no ROA of AS4847 covers them; only the first 10 are checked).
  • Warning: 143 of 887 announced prefixes have no IRR route object: 118.194.134.0/23, 45.124.21.0/24, 118.187.56.0/24, 218.240.7.0/24, 101.96.132.0/23 (+138).
  • Info: 2 upstreams and peers, 62 downstream networks seen.
HolderCNIX-AP - China Networks Inter-Exchange
IPv4 prefixes876
IPv6 prefixes11
RPKI732 valid · 12 invalid · 9 not found · 134 not looked up
Without IRR route object143
Downstream networks62
Routes to fix
PrefixRPKI
123.58.232.0/22 RPKI invalid
123.58.232.0/24 RPKI invalid
123.58.233.0/24 RPKI invalid
123.58.234.0/24 RPKI invalid
123.58.235.0/24 RPKI invalid
123.58.236.0/24 RPKI invalid
123.58.237.0/24 RPKI invalid
123.58.238.0/23 RPKI invalid
123.58.238.0/24 RPKI invalid
123.58.239.0/24 RPKI invalid
222.249.231.0/24 RPKI invalid
43.240.202.0/24 RPKI invalid
49.221.26.0/23 No ROA
49.221.64.0/19 No ROA
49.221.128.0/19 No ROA
60.247.0.0/17 No ROA
60.247.0.0/19 No ROA
60.247.28.0/24 No ROA
60.247.32.0/19 No ROA
60.247.45.0/24 No ROA
60.247.64.0/19 No ROA

Upstreams and peers seen to the left 2

Announced prefixes 887

1.119.128.0/19 1.119.160.0/19 1.119.173.0/24 1.119.178.0/23 1.119.192.0/21 1.119.200.0/22 1.119.208.0/23 1.119.210.0/23 1.202.0.0/17 1.202.17.0/24 1.202.128.0/17 1.202.143.0/24 1.202.217.0/24 1.202.224.0/24 1.202.228.0/24 1.202.231.0/24 1.202.237.0/24 1.203.0.0/16 1.203.0.0/18 1.203.90.0/24 1.203.91.0/24 1.203.105.0/24 1.203.128.0/20 36.110.0.0/17 36.110.14.0/24 36.110.24.0/24 36.110.28.0/24 36.110.38.0/24 36.110.60.0/24 36.110.69.0/24 36.110.82.0/24 36.110.112.0/24 36.110.114.0/24 36.110.118.0/24 36.110.119.0/24 36.110.120.0/24 36.110.121.0/24 36.112.0.0/16 36.112.3.0/24 36.112.20.0/24 36.112.22.0/24 36.112.27.0/24 36.112.30.0/24 36.112.31.0/24 36.112.39.0/24 36.112.48.0/22 36.112.56.0/24 36.112.63.0/24 36.112.89.0/24 36.112.97.0/24 36.112.101.0/24 36.112.107.0/24 36.112.113.0/24 36.112.115.0/24 36.112.121.0/24 36.112.122.0/24 36.112.140.0/23 36.112.151.0/24 36.112.152.0/24 36.112.162.0/24 36.112.166.0/24 36.112.228.0/24 36.112.232.0/24 36.112.248.0/24 43.226.237.0/24 43.226.239.0/24 43.227.140.0/22 43.229.184.0/24 43.240.202.0/24 43.243.12.0/22 43.254.25.0/24 43.254.26.0/23 43.254.88.0/22 43.254.200.0/22 45.124.20.0/24 45.124.21.0/24 45.124.22.0/24 45.124.23.0/24 45.126.112.0/22 45.127.144.0/21 45.251.20.0/22 45.251.20.0/23 45.251.20.0/24 45.251.21.0/24 45.251.22.0/23 45.251.22.0/24 45.251.23.0/24 45.254.8.0/24 45.254.9.0/24 49.221.26.0/23 49.221.64.0/19 49.221.128.0/19 58.68.236.0/24 58.68.247.0/24 58.116.0.0/18 58.116.64.0/18 58.116.128.0/18 58.116.192.0/18 58.117.0.0/18 58.117.64.0/18

Showing the first 100.

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.
NameCNIX-AP
HandleAS4847
RangeAS4847
CountryCN
Statusactive
Registered2008-09-04T06:40:27Z
Last changed2021-06-15T08:06:11Z
Abuse contactanti-spam@chinatelecom.cn
Allocation
Registry (RIR)APNIC
CountryChina (CN)
Delegated on1996-09-10
StatusAllocated
Delegated rangeAS4847

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

Contacts
RoleNameEmail
abuse IRT-CHINANET-CN anti-spam@chinatelecom.cn
administrative Liang Zhiping lzp@public.bta.net.cn
technical Wanshu Zhou zhouws@public.bta.net.cn

Source: https://rdap.apnic.net/autnum/4847. 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: AS4847 is in PeeringDB as CNIX-AP.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
NetworkCNIX-AP
AS numberAS4847
Type, Not Disclosed
TrafficNot Disclosed
Ratio requiredNo
Last updated2025-02-17

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup