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

AS57695 ·

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

Warning: AS57695 (MISAKA) announces 11 IPv4 and 27 IPv6 prefixes. 3 warnings

AS pageAS57695
HolderMISAKA Misaka Network, Inc.
AllocationRIPE NCC, United States (US), allocated 2017-06-20
Prefixes (IPv4 / IPv6)11 / 27
RPKI valid66% (25 / 38)
Upstreams and peers10
Peering policyOpen

What to fix

  1. Warning

    10 of 38 announced prefixes have no ROA (RPKI not found): 2a0b:4343:11::/48, 2a0b:4343:41::/48, 2a0b:4343:51::/48, 2a0b:4343:1002::/48, 2a0b:4343:1022::/48 (+5).

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

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

    2a0b:4343:11::/48 AS57695 max-length /48
    2a0b:4343:41::/48 AS57695 max-length /48
    2a0b:4343:51::/48 AS57695 max-length /48
    2a0b:4343:1002::/48 AS57695 max-length /48
    2a0b:4343:1022::/48 AS57695 max-length /48
    2a0b:4343:1041::/48 AS57695 max-length /48
    2a0b:4343:1042::/48 AS57695 max-length /48
    2a0b:4343:1043::/48 AS57695 max-length /48
    2a0b:4343:1071::/48 AS57695 max-length /48
    2a0b:4343:2013::/48 AS57695 max-length /48

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 38 announced prefixes have no IRR route object: 2407:b9c0:e800::/40.

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

    route6: 2407:b9c0:e800::/40
    origin: AS57695

    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 10 of 38 announced prefixes have no ROA (RPKI not found): 2a0b:4343:11::/48, 2a0b:4343:41::/48, 2a0b:4343:51::/48, 2a0b:4343:1002::/48, 2a0b:4343:1022::/48 (+5).
  • Pass: AS57695 announces 11 IPv4 and 27 IPv6 prefixes.
  • Warning: 10 of 38 announced prefixes have no ROA (RPKI not found): 2a0b:4343:11::/48, 2a0b:4343:41::/48, 2a0b:4343:51::/48, 2a0b:4343:1002::/48, 2a0b:4343:1022::/48 (+5).
  • Info: 25 of 38 announced prefixes are RPKI valid.
  • Info: The RPKI state of 3 prefixes was not looked up (no ROA of AS57695 covers them; only the first 10 are checked).
  • Warning: 1 of 38 announced prefixes have no IRR route object: 2407:b9c0:e800::/40.
  • Info: 10 upstreams and peers, 43 downstream networks seen.
HolderMISAKA Misaka Network, Inc.
IPv4 prefixes11
IPv6 prefixes27
RPKI25 valid · 10 not found · 3 not looked up
Without IRR route object1
Downstream networks43

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

Open in ASN & BGP prefix lookup
Registration The registry is limiting how often it can be asked. Please try again in a minute.
PeeringDB No public NOC, policy or technical contact.
  • Pass: AS57695 is in PeeringDB as Misaka Network, Inc..
  • Info: Peering policy: Open.
  • Info: Present at 3 internet exchanges with 3 ports (2.1G in total).
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2023-02-13.
NetworkMisaka Network, Inc. (Misaka.io)
AS numberAS57695
TypeNSP, Global
Websitehttps://www.misaka.io/
IRR as-setAS-MISAKA
Prefixes (IPv4 / IPv6)300 / 600
Traffic100-200Gbps, Balanced
Peering policyOpen
Policy URLhttps://docs.misaka.io/network/peering
LocationsPreferred
Ratio requiredNo
ContractsNot Required
Looking glasshttps://ping.sx/
Last updated2023-02-13
Contacts
Abuseabuse@misaka.email

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup