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

AS52054 ·

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

Warning: AS52054 (dataroute dataroute srl) announces 3 IPv4 and 0 IPv6 prefixes. 2 warnings

AS pageAS52054
Holderdataroute dataroute srl
AllocationRIPE NCC, Italy (IT), allocated 2016-06-23
Prefixes (IPv4 / IPv6)3 / 0
RPKI valid100% (3 / 3)
Upstreams and peers1

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

    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: AS52054 announces 3 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Pass: All 3 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS200311): an outage there takes the whole network off the internet.
Holderdataroute dataroute srl
IPv4 prefixes3
IPv6 prefixes0
RPKI3 valid
Downstream networks0

Upstreams and peers seen to the left 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