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

AS17620 ·

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

Warning: AS17620 (CNCGROUP-BJ) announces nothing right now. 1 warning

AS pageAS17620
HolderCNCGROUP-BJ - CNCGROUP IP network of Beijing region MAN network
AllocationAPNIC, China (CN), allocated 2001-01-18
Prefixes (IPv4 / IPv6)0 / 0

What to fix

  1. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI Partial result: RIPEstat did not return the irr in time.
  • Info: Partial result: RIPEstat did not return the irr in time.
  • Info: AS17620 is not announcing anything right now.
HolderCNCGROUP-BJ - CNCGROUP IP network of Beijing region MAN network
IPv4 prefixes0
IPv6 prefixes0
Downstream networks0

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.
NameCNCGROUP-BJ
HandleAS17620
RangeAS17620
CountryCN
Statusactive
Registered2008-09-04T06:40:30Z
Last changed2023-10-21T03:42:06Z
Abuse contacthqs-ipabuse@chinaunicom.cn
Allocation
Registry (RIR)APNIC
CountryChina (CN)
Delegated on2001-01-18
StatusAllocated
Delegated rangeAS17620 – AS17623

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

Contacts
RoleNameEmail
abuse IRT-CU-CN hqs-ipabuse@chinaunicom.cn
administrative, technical CNCGroup Hostmaster hqs-ipabuse@chinaunicom.cn

Source: https://rdap.apnic.net/autnum/17620. 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 PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup