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

AS138586 ·

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

Warning: AS138586 (GAOSHICLOUD-AS-AP) announces nothing right now. 1 warning

AS pageAS138586
HolderGAOSHICLOUD-AS-AP - CodecCloud (HK) Limited
AllocationAPNIC, Hong Kong SAR China (HK), allocated 2019-01-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 Partial result: RIPEstat did not return the irr in time.
  • Info: Partial result: RIPEstat did not return the irr in time.
  • Info: AS138586 is not announcing anything right now.
HolderGAOSHICLOUD-AS-AP - CodecCloud (HK) 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.
NameGAOSHICLOUD-AS-AP
HandleAS138586
RangeAS138586
CountryHK
Statusactive
Registered2019-01-30T05:33:04Z
Last changed2020-07-20T12:18:22Z
Abuse contactabuse@moecloud.asia
Allocation
Registry (RIR)APNIC
CountryHong Kong SAR China (HK)
Delegated on2019-01-30
StatusAllocated
Delegated rangeAS138586

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

Contacts
RoleNameEmail
administrative, technical CodecCloud NOC abuse@moecloud.asia
registrant CodecCloud (HK) Limited noc@moecloud.asia
abuse IRT-CODECCLOUD-HK abuse@moecloud.asia

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