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

AS201052 ·

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

Warning: AS201052 (GOVCERT-RU-AS) announces 11 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS201052
HolderGOVCERT-RU-AS Autonomous nonprofit organisation "Computer Incident Response Center"
AllocationRIPE NCC, Russia (RU), allocated 2015-02-10
Prefixes (IPv4 / IPv6)11 / 0
RPKI valid0% (0 / 11)
Upstreams and peers2

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    10 of 11 announced prefixes have no ROA (RPKI not found): 144.206.64.0/20, 144.206.80.0/21, 144.206.88.0/24, 144.206.89.0/24, 144.206.90.0/24 (+5).

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

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

    144.206.64.0/20 AS201052 max-length /20
    144.206.80.0/21 AS201052 max-length /21
    144.206.88.0/24 AS201052 max-length /24
    144.206.89.0/24 AS201052 max-length /24
    144.206.90.0/24 AS201052 max-length /24
    144.206.91.0/24 AS201052 max-length /24
    144.206.92.0/24 AS201052 max-length /24
    144.206.93.0/24 AS201052 max-length /24
    144.206.94.0/24 AS201052 max-length /24
    144.206.95.0/24 AS201052 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    2 of 11 announced prefixes have no IRR route object: 144.206.64.0/20, 144.206.80.0/21.

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

    route: 144.206.64.0/20
    origin: AS201052
    
    route: 144.206.80.0/21
    origin: AS201052

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS201052 announces 11 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 10 of 11 announced prefixes have no ROA (RPKI not found): 144.206.64.0/20, 144.206.80.0/21, 144.206.88.0/24, 144.206.89.0/24, 144.206.90.0/24 (+5).
  • Info: The RPKI state of 1 prefixes was not looked up (no ROA of AS201052 covers them; only the first 10 are checked).
  • Warning: 2 of 11 announced prefixes have no IRR route object: 144.206.64.0/20, 144.206.80.0/21.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderGOVCERT-RU-AS Autonomous nonprofit organisation "Computer Incident Response Center"
IPv4 prefixes11
IPv6 prefixes0
RPKI10 not found · 1 not looked up
Without IRR route object2
Downstream networks0
Routes to fix

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 The registry is limiting how often it can be asked. Please try again in a minute.
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