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

AS142616 ·

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

Warning: AS142616 (MNI-AS-AP) announces 3 IPv4 and 7 IPv6 prefixes. 2 warnings

AS pageAS142616
HolderMNI-AS-AP - Misaka Network, Inc.
AllocationAPNIC, United States (US), allocated 2021-08-02
Prefixes (IPv4 / IPv6)3 / 7
RPKI valid100% (10 / 10)
Upstreams and peers2
Peering policySelective

What to fix

  1. Warning

    6 of 10 announced prefixes have no IRR route object: 2407:b9c0:f76::/48, 2407:b9c0:f73::/48, 2407:b9c0:f75::/48, 2407:b9c0:f71::/48, 2407:b9c0:f72::/48 (+1).

    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 AS142616 in your RIR’s IRR database (or RADB).

    route6: 2407:b9c0:f76::/48
    origin: AS142616
    
    route6: 2407:b9c0:f73::/48
    origin: AS142616
    
    route6: 2407:b9c0:f75::/48
    origin: AS142616

    Open in ASN & BGP prefix lookup

  2. 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 6 of 10 announced prefixes have no IRR route object: 2407:b9c0:f76::/48, 2407:b9c0:f73::/48, 2407:b9c0:f75::/48, 2407:b9c0:f71::/48, 2407:b9c0:f72::/48 (+1).
  • Pass: AS142616 announces 3 IPv4 and 7 IPv6 prefixes.
  • Pass: All 10 announced prefixes are RPKI valid.
  • Warning: 6 of 10 announced prefixes have no IRR route object: 2407:b9c0:f76::/48, 2407:b9c0:f73::/48, 2407:b9c0:f75::/48, 2407:b9c0:f71::/48, 2407:b9c0:f72::/48 (+1).
  • Info: 2 upstreams and peers, 15 downstream networks seen.
HolderMNI-AS-AP - Misaka Network, Inc.
IPv4 prefixes3
IPv6 prefixes7
RPKI10 valid
Without IRR route object6
Downstream networks15

Upstreams and peers seen to the left 2

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.
NameMNI-AS-AP
HandleAS142616
RangeAS142616
CountryJP
Statusactive
Registered2021-08-02T00:31:15Z
Last changed2021-08-08T23:48:35Z
Abuse contactabuse-jp@misaka.email
Allocation
Registry (RIR)APNIC
CountryUnited States (US)
Delegated on2021-08-02
StatusAllocated
Delegated rangeAS142616

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

Contacts
RoleNameEmail
registrant Misaka Network, Inc. support@misaka.io
abuse IRT-MISAKAJP-AP abuse-jp@misaka.email
administrative, technical Network Operations Center noc+apnic@misaka.io

Source: https://rdap.apnic.net/autnum/142616. 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: AS142616 is in PeeringDB as Misaka Network (AS142616).
  • Info: Peering policy: Selective.
  • Info: No internet exchange ports are listed.
  • Warning: No public NOC, policy or technical contact.
NetworkMisaka Network (AS142616)
AS numberAS142616
Type, Not Disclosed
Websitehttps://www.misaka.io/locations/nrt04
IRR as-setAS-MISAKA
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policySelective
Policy URLhttps://as917.peeringdb.com/
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-04-09

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup