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

AS134666 ·

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

Warning: AS134666 (HoshiNetwork) announces 0 IPv4 and 11 IPv6 prefixes. 3 warnings

AS pageAS134666
HolderHoshiNetwork - Hoshi Network
AllocationAPNIC, Hong Kong SAR China (HK), allocated 2018-08-27
Prefixes (IPv4 / IPv6)0 / 11
RPKI valid73% (8 / 11)
Upstreams and peers9
Peering policyOpen

What to fix

  1. Warning

    3 of 11 announced prefixes have no ROA (RPKI not found): 2602:fed2:7010::/48, 2602:feda:aee::/48, 2602:feda:aef::/48.

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

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

    2602:fed2:7010::/48 AS134666 max-length /48
    2602:feda:aee::/48 AS134666 max-length /48
    2602:feda:aef::/48 AS134666 max-length /48

    Open in RPKI / ROA validator Guide

  2. Warning

    2 of 11 announced prefixes have no IRR route object: 2602:feda:aef::/48, 2602:fed2:7010::/48.

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS134666 in your RIR’s IRR database (or RADB).

    route6: 2602:feda:aef::/48
    origin: AS134666
    
    route6: 2602:fed2:7010::/48
    origin: AS134666

    Open in ASN & BGP prefix lookup

  3. 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 11 announced prefixes have no ROA (RPKI not found): 2602:fed2:7010::/48, 2602:feda:aee::/48, 2602:feda:aef::/48.
  • Pass: AS134666 announces 0 IPv4 and 11 IPv6 prefixes.
  • Warning: 3 of 11 announced prefixes have no ROA (RPKI not found): 2602:fed2:7010::/48, 2602:feda:aee::/48, 2602:feda:aef::/48.
  • Info: 8 of 11 announced prefixes are RPKI valid.
  • Warning: 2 of 11 announced prefixes have no IRR route object: 2602:feda:aef::/48, 2602:fed2:7010::/48.
  • Info: 9 upstreams and peers, 1 downstream networks seen.
HolderHoshiNetwork - Hoshi Network
IPv4 prefixes0
IPv6 prefixes11
RPKI8 valid · 3 not found
Without IRR route object2
Downstream networks1
Routes to fix

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.
NameHoshiNetwork
HandleAS134666
RangeAS134666
CountryHK
Statusactive
Registered2022-03-16T05:07:06Z
Last changed2022-03-17T01:39:28Z
Abuse contactmoc@enp2s0.net
Allocation
Registry (RIR)APNIC
CountryHong Kong SAR China (HK)
Delegated on2018-08-27
StatusAllocated
Delegated rangeAS134666

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

Contacts
RoleNameEmail
technical, administrative Hoshi Network Administrator moc@enp2s0.net
registrant Cat Networks K.K. info@catnetworks.co.jp
abuse IRT-ATR-HK moc@enp2s0.net

Source: https://rdap.apnic.net/autnum/134666. 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 public NOC, policy or technical contact.
  • Pass: AS134666 is in PeeringDB as Hoshi Network.
  • Info: Peering policy: Open.
  • Info: Present at 6 internet exchanges with 6 ports (22.1G in total).
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2023-05-13.
NetworkHoshi Network (Hoshi Hosting)
AS numberAS134666
TypeEducational/Research, Global
IRR as-setAS-HOSHI-NETWORK
Prefixes (IPv4 / IPv6)0 / 100
Traffic20-100Mbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2023-05-13

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup