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

AS55739 ·

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

Warning: AS55739 (CNISP-UNION) announces nothing right now. 1 warning

AS pageAS55739
HolderCNISP-UNION - CNISP-Union Technology (Beijing) Co., Ltd
AllocationAPNIC, China (CN), allocated 2010-08-30
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 AS55739 is not announcing anything right now.
  • Info: AS55739 is not announcing anything right now.
HolderCNISP-UNION - CNISP-Union Technology (Beijing) Co., Ltd
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.
NameCNISP-UNION
HandleAS55739
RangeAS55739
CountryCN
Statusactive
Registered2010-08-30T11:53:47Z
Last changed2020-07-07T04:54:12Z
Abuse contactsupport@cnispgroup.com
Allocation
Registry (RIR)APNIC
CountryChina (CN)
Delegated on2010-08-30
StatusAllocated
Delegated rangeAS55739

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

Contacts
RoleNameEmail
administrative Dong Yinliang linyue@cnispgroup.com
abuse IRT-NET-AP support@cnispgroup.com
technical Wang Fei linyue@cnispgroup.com
registrant Beijing CNISP Technology Co., Ltd. ip@cnispgroup.com

Source: https://rdap.apnic.net/autnum/55739. 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