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

AS137944 · 

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

Warning: AS137944 (CLOUDBASE-AS-AP) announces nothing right now. 1 warning

AS pageAS137944
HolderCLOUDBASE-AS-AP - HONG KONG CLOUDBASE TECHNOLOGY CO., LIMITED
AllocationAPNIC, Hong Kong SAR China (HK), allocated 2018-07-03
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 AS137944 is not announcing anything right now.
  • Info: AS137944 is not announcing anything right now.
HolderCLOUDBASE-AS-AP - HONG KONG CLOUDBASE TECHNOLOGY CO., LIMITED
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.
NameCLOUDBASE-AS-AP
HandleAS137944
RangeAS137944
CountryHK
Statusactive
Registered2023-08-14T07:34:36Z
Last changed2023-08-14T07:34:36Z
Abuse contactchenwenjie@idcloudbase.com
Allocation
Registry (RIR)APNIC
CountryHong Kong SAR China (HK)
Delegated on2018-07-03
StatusAllocated
Delegated rangeAS137944

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

Contacts
RoleNameEmail
administrative, technical HONG KONG CLOUDBASE TECHNOLOGY CO LIMITED admini zhuhaiqin@gdcloudbase.com
registrant HONG KONG CLOUDBASE TECHNOLOGY CO., LIMITED chenwenjie@idcloudbase.com
abuse IRT-CLOUDBASE-HK chenwenjie@idcloudbase.com

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