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

AS134833 · 

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

Warning: AS134833 (LIHGL-HK) announces nothing right now. 1 warning

AS pageAS134833
HolderLIHGL-HK - 24.HK BGP FAST GLOBAL
AllocationAPNIC, Hong Kong SAR China (HK), allocated 2015-11-25
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 AS134833 is not announcing anything right now.
  • Info: AS134833 is not announcing anything right now.
HolderLIHGL-HK - 24.HK BGP FAST GLOBAL
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.
NameLIHGL-HK
HandleAS134833
RangeAS134833
CountryHK
Statusactive
Registered2015-11-24T23:46:04Z
Last changed2020-07-07T05:22:28Z
Abuse contactkchan2789@gmail.com
Allocation
Registry (RIR)APNIC
CountryHong Kong SAR China (HK)
Delegated on2015-11-25
StatusAllocated
Delegated rangeAS134833

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

Contacts
RoleNameEmail
registrant LANLIAN INTERNATIONAL HOLDING GROUP LIMITED kchan2789@gmail.com
administrative, technical LANLIAN INTL HOLDING GROUP LIMITED administrator mail@nlidc.com
abuse IRT-LIHGL-HK kchan2789@gmail.com

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