Network report

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 10 announced prefixes have no ROA (RPKI not found): 12.43.214.0/24, 12.156.76.0/24, 38.67.195.0/24, 38.86.47.0/24, 38.94.32.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 AS40593 and a max length equal to the prefix length:

   12.43.214.0/24 AS40593 max-length /24
   12.156.76.0/24 AS40593 max-length /24
   38.67.195.0/24 AS40593 max-length /24
   38.86.47.0/24 AS40593 max-length /24
   38.94.32.0/24 AS40593 max-length /24
   38.101.73.0/24 AS40593 max-length /24
   38.101.75.0/24 AS40593 max-length /24
   38.126.217.0/24 AS40593 max-length /24
   38.127.115.0/24 AS40593 max-length /24
   144.86.168.0/24 AS40593 max-length /24

   Open in RPKI / ROA validator Guide

3. Warning

   2 of 10 announced prefixes have no IRR route object: 12.43.214.0/24, 12.156.76.0/24.

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

   route: 12.43.214.0/24
   origin: AS40593
   
   route: 12.156.76.0/24
   origin: AS40593

   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