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

AS38738 ·

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

Warning: AS38738 (LCS-AS-VN) announces 10 IPv4 and 1 IPv6 prefixes. 1 warning

AS pageAS38738
HolderLCS-AS-VN - L.C.S Company.,ltd
AllocationAPNIC, Vietnam (VN), allocated 2007-09-14
Prefixes (IPv4 / IPv6)10 / 1
RPKI valid100% (11 / 11)
Upstreams and peers3

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 AS38738 announces 10 IPv4 and 1 IPv6 prefixes.
  • Pass: AS38738 announces 10 IPv4 and 1 IPv6 prefixes.
  • Pass: All 11 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 3 upstreams and peers, 3 downstream networks seen.
HolderLCS-AS-VN - L.C.S Company.,ltd
IPv4 prefixes10
IPv6 prefixes1
RPKI11 valid
Downstream networks3

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.
NameLCS-AS-VN
HandleAS38738
RangeAS38738
CountryVN
Statusactive
Registered2008-11-14T07:30:54Z
Last changed2017-11-18T07:33:34Z
Abuse contacthm-changed@vnnic.vn
Allocation
Registry (RIR)APNIC
CountryVietnam (VN)
Delegated on2007-09-14
StatusAllocated
Delegated rangeAS38725 – AS38739

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

Contacts
RoleNameEmail
administrative Hoang Manh Toan toanhoang@lcs.com.vn
abuse IRT-VNNIC-AP hm-changed@vnnic.vn
technical Nguyen Van Hiep hiepnguyen@lcs.com.vn

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