bgpreport

Network · data from 2026-11-12

AS30295 SmarttNet

Registry name: 2ICSYSTEMSINC - Smartt Inc., CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30295, 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.

69.31.172.0/22 No ROA Other IRR onlyRADB 673 100% 67
204.187.64.0/24 No ROA Other IRR onlyRADB 673 100% 67
69.31.160.0/21 No ROA RIR databaseARIN 673 100% 67
69.31.170.0/23 No ROA RIR databaseARIN 673 100% 67
69.31.176.0/20 No ROA RIR databaseARIN, RADB 673 100% 67
69.31.168.0/24 No ROA RIR databaseARIN 671 100% 68
69.31.169.0/24 No ROA RIR databaseARIN 671 100% 68
2606:3000:c000::/48 No ROA RIR databaseARIN 635 100% 69
2606:3000:e000::/35 No ROA RIR databaseARIN 635 100% 69
2606:3000::/35 No ROA RIR databaseARIN 634 100% 70

AS-SET

AS30295's PeeringDB record names no 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 22 are in fix.csv.

  • ROA: none10
  • Route object: RIR2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none69.31.172.0/22No ROA covers it. Add a ROA for AS30295, maxLength 22.673 of 673
Route object: RIR69.31.172.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none204.187.64.0/24No ROA covers it. Add a ROA for AS30295, maxLength 24.673 of 673
Route object: RIR204.187.64.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none69.31.160.0/21No ROA covers it. Add a ROA for AS30295, maxLength 21.673 of 673
ROA: none69.31.170.0/23No ROA covers it. Add a ROA for AS30295, maxLength 23.673 of 673
ROA: none69.31.176.0/20No ROA covers it. Add a ROA for AS30295, maxLength 20.673 of 673
ROA: none69.31.168.0/24No ROA covers it. Add a ROA for AS30295, maxLength 24.671 of 673
ROA: none69.31.169.0/24No ROA covers it. Add a ROA for AS30295, maxLength 24.671 of 673
ROA: none2606:3000:c000::/48No ROA covers it. Add a ROA for AS30295, maxLength 48.635 of 636
ROA: none2606:3000:e000::/35No ROA covers it. Add a ROA for AS30295, maxLength 35.635 of 636
ROA: none2606:3000::/35No ROA covers it. Add a ROA for AS30295, maxLength 35.634 of 636

Route objects not announced

Route objects with origin AS30295 whose prefix no peer sees AS30295 announce. Many are kept on purpose (backup routes, space announced only in some places).

57.234.221.0/24RADBNo ROA
69.31.160.0/19RADBNo ROA
69.31.160.0/20ARIN, RADBNo ROA
69.67.184.0/24ARINNo ROA
96.9.108.0/22RADBNo ROA
199.60.233.0/24RADBNo ROA
199.60.234.0/23RADBNo ROA
199.60.234.0/24RADBNo ROA
199.60.236.0/24RADBNo ROA
2606:3000::/32RADBNo ROA

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.