bgpreport

Network · data from 2026-11-12

AS403005 BLATANTHOST - Blatant

Registry name: BLATANTHOST - Blatant, SC · not in PeeringDB

13IPv4 routes 46.2% RPKI valid · 38.5% with a route object
0IPv6 routes
4RPKI invalid 0 origin · 4 maxLength
3No ROA 8 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS403005, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS403005, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

31.56.19.70/32 Invalid: maxLength Nonecovered by 31.56.19.0/24 1 0%low visibility 1
31.56.19.72/32 Invalid: maxLength Nonecovered by 31.56.19.0/24 1 0%low visibility 1
31.56.19.73/32 Invalid: maxLength Nonecovered by 31.56.19.0/24 1 0%low visibility 1
31.56.19.111/32 Invalid: maxLength Nonecovered by 31.56.19.0/24 1 0%low visibility 1
196.251.100.0/24 No ROA None 670 100% 67
196.251.121.0/24 No ROA None 668 99% 67
196.251.102.0/24 No ROA None 667 99% 67
46.151.182.0/24 Valid Other origin only 661 98% 66
31.56.19.0/24 Valid RIR databaseRIPE 668 99% 66
64.89.160.0/24 Valid RIR databaseARIN 665 99% 66
36.255.97.0/24 Valid RIR databaseAPNIC 663 99% 66
64.89.161.0/24 Valid RIR databaseARIN 663 99% 66
43.228.157.0/24 Valid RIR databaseAPNIC 661 98% 66

AS-SET

AS403005 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 15 are in fix.csv.

  • ROA: maxLength4
  • ROA: none3
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: maxLength31.56.19.70/32ROA 31.56.19.0/24 AS403005 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.56.19.70/32.1 of 673
Route object: none31.56.19.70/32No route object for it. A route object for 31.56.19.0/24 with origin AS403005 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS403005 in the RIR database for the space.1 of 673
ROA: maxLength31.56.19.72/32ROA 31.56.19.0/24 AS403005 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.56.19.72/32.1 of 673
Route object: none31.56.19.72/32No route object for it. A route object for 31.56.19.0/24 with origin AS403005 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS403005 in the RIR database for the space.1 of 673
ROA: maxLength31.56.19.73/32ROA 31.56.19.0/24 AS403005 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.56.19.73/32.1 of 673
Route object: none31.56.19.73/32No route object for it. A route object for 31.56.19.0/24 with origin AS403005 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS403005 in the RIR database for the space.1 of 673
ROA: maxLength31.56.19.111/32ROA 31.56.19.0/24 AS403005 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 31.56.19.111/32.1 of 673
Route object: none31.56.19.111/32No route object for it. A route object for 31.56.19.0/24 with origin AS403005 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS403005 in the RIR database for the space.1 of 673
ROA: none196.251.100.0/24No ROA covers it. Add a ROA for AS403005, maxLength 24.670 of 673
Route object: none196.251.100.0/24No route object for it. Add a route object with origin AS403005 in the RIR database for the space.670 of 673
ROA: none196.251.121.0/24No ROA covers it. Add a ROA for AS403005, maxLength 24.668 of 673
Route object: none196.251.121.0/24No route object for it. Add a route object with origin AS403005 in the RIR database for the space.668 of 673
ROA: none196.251.102.0/24No ROA covers it. Add a ROA for AS403005, maxLength 24.667 of 673
Route object: none196.251.102.0/24No route object for it. Add a route object with origin AS403005 in the RIR database for the space.667 of 673
Route object: none46.151.182.0/24Route objects for it name AS36680. Add a route object with origin AS403005 in the RIR database for the space.661 of 673

Route objects not announced

Every route object with origin AS403005 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.