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

AS38633 · 

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

Warning: AS38633 (VCIU-NET-AS) announces 3 IPv4 and 1 IPv6 prefixes. 4 warnings

AS pageAS38633
HolderVCIU-NET-AS - Value Core Inc.
AllocationAPNIC, Japan (JP), allocated 2007-08-20
Prefixes (IPv4 / IPv6)3 / 1
RPKI valid25% (1 / 4)
Upstreams and peers2
Peering policyOpen

What to fix

  1. Warning

    3 of 4 announced prefixes have no ROA (RPKI not found): 103.120.184.0/22, 116.197.168.0/21, 180.211.84.0/22.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS38633 and a max length equal to the prefix length:

    103.120.184.0/22 AS38633 max-length /22
116.197.168.0/21 AS38633 max-length /21
180.211.84.0/22 AS38633 max-length /22

    Open in RPKI / ROA validator Guide

  2. Warning

    No abuse contact is published for AS38633.

    Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.

    Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.

    Open in WHOIS / RDAP lookup

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 3 of 4 announced prefixes have no ROA (RPKI not found): 103.120.184.0/22, 116.197.168.0/21, 180.211.84.0/22.
  • Pass: AS38633 announces 3 IPv4 and 1 IPv6 prefixes.
  • Warning: 3 of 4 announced prefixes have no ROA (RPKI not found): 103.120.184.0/22, 116.197.168.0/21, 180.211.84.0/22.
  • Info: 1 of 4 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderVCIU-NET-AS - Value Core Inc.
IPv4 prefixes3
IPv6 prefixes1
RPKI1 valid · 3 not found
Downstream networks1
Routes to fix
PrefixRPKI
103.120.184.0/22 No ROA
116.197.168.0/21 No ROA
180.211.84.0/22 No ROA

Upstreams and peers seen to the left 2

AS7529 NetIRD AS17511 OPTAGE

Announced prefixes 4

103.120.184.0/22 116.197.168.0/21 180.211.84.0/22 2403:8e00::/32

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration No abuse contact is published for AS38633.
  • Pass: Found at rdap.apnic.net.
  • Warning: No abuse contact is published for AS38633.
NameVCIU-NET-AS
HandleAS38633
RangeAS38633
CountryJP
Statusactive
Last changed2008-01-31T23:50:11Z
Allocation
Registry (RIR)APNIC
CountryJapan (JP)
Delegated on2007-08-20
StatusAllocated
Delegated rangeAS38627 – AS38656

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

Contacts
RoleNameEmail
technical, administrative Japan Network Information Center hostmaster@nic.ad.jp
technical, administrative JP00026123

Source: https://rdap.apnic.net/autnum/38633. 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 No IRR as-set is listed.
  • Pass: AS38633 is in PeeringDB as Value Core.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-10-26.
NetworkValue Core
AS numberAS38633
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-10-26

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup