Network report

What to fix

1. Problem

   2 of 7 announced prefixes are RPKI invalid: 103.158.65.0/24, 116.212.177.0/24.

   A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

   Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

   Open in RPKI / ROA validator Guide

2. 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

3. Warning

   5 of 7 announced prefixes have no ROA (RPKI not found): 38.109.201.0/24, 38.109.226.0/24, 45.178.213.0/24, 103.148.204.0/24, 167.253.45.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 AS5 and a max length equal to the prefix length:

   38.109.201.0/24 AS5 max-length /24
   38.109.226.0/24 AS5 max-length /24
   45.178.213.0/24 AS5 max-length /24
   103.148.204.0/24 AS5 max-length /24
   167.253.45.0/24 AS5 max-length /24

   Open in RPKI / ROA validator Guide

4. Warning

   5 of 7 announced prefixes have no IRR route object: 45.178.213.0/24, 38.109.201.0/24, 167.253.45.0/24, 116.212.177.0/24, 38.109.226.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 AS5 in your RIR’s IRR database (or RADB).

   route: 45.178.213.0/24
   origin: AS5
   
   route: 38.109.201.0/24
   origin: AS5
   
   route: 167.253.45.0/24
   origin: AS5

   Open in ASN & BGP prefix lookup

5. Warning

   PeeringDB did not answer: HTTP 404

   Fix: Try again in a minute.

   Open in PeeringDB lookup

Checks