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

AS43199 ·

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

Warning: AS43199 (UEH-AS) announces 1 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS43199
HolderUEH-AS AO "Edinaya Evropa - Holding"
AllocationRIPE NCC, Russia (RU), allocated 2007-06-22
Prefixes (IPv4 / IPv6)1 / 0
RPKI valid0% (0 / 1)
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

    1 of 1 announced prefixes have no ROA (RPKI not found): 77.108.86.0/24.

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

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

    77.108.86.0/24 AS43199 max-length /24

    Open in RPKI / ROA validator Guide

  3. 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: AS43199 announces 1 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 1 announced prefixes have no ROA (RPKI not found): 77.108.86.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderUEH-AS AO "Edinaya Evropa - Holding"
IPv4 prefixes1
IPv6 prefixes0
RPKI1 not found
Downstream networks0
Routes to fix
PrefixRPKI
77.108.86.0/24 No ROA

Upstreams and peers seen to the left 2

Announced prefixes 1

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