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

   2 of 2 announced prefixes have no ROA (RPKI not found): 102.223.248.0/24, 102.223.249.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 AS328634 and a max length equal to the prefix length:

   102.223.248.0/24 AS328634 max-length /24
   102.223.249.0/24 AS328634 max-length /24

   Open in RPKI / ROA validator Guide

3. Warning

   1 of 2 announced prefixes have no IRR route object: 102.223.249.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 AS328634 in your RIR’s IRR database (or RADB).

   route: 102.223.249.0/24
   origin: AS328634

   Open in ASN & BGP prefix lookup

4. Warning

   No abuse contact is published for AS328634.

   Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.

   Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.

   Open in WHOIS / RDAP lookup

5. Warning

   PeeringDB did not answer: HTTP 404

   Fix: Try again in a minute.

   Open in PeeringDB lookup

Checks