bgpreport

Network · data from 2026-11-12

AS394303 BIGSCOOTS

Registry name: BIGSCOOTS - BigScoots, US · PeeringDB

11IPv4 routes 9.1% RPKI valid · 100.0% with a route object
0IPv6 routes
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
18Route objects not announced registered with origin AS394303, seen from no peer

Announced routes

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

38.22.240.0/21 No ROA Other IRR onlyRADB 673 100% 70
38.58.224.0/21 No ROA Other IRR onlyRADB 673 100% 70
38.65.224.0/22 No ROA Other IRR onlyRADB 673 100% 70
154.12.120.0/21 No ROA Other IRR onlyRADB 673 100% 70
154.18.240.0/21 No ROA Other IRR onlyRADB 673 100% 70
74.121.204.0/22 No ROA RIR databaseALTDB, ARIN, RADB 673 100% 70
167.253.104.0/22 No ROA RIR databaseARIN, RADB 673 100% 70
198.175.24.0/22 No ROA RIR databaseALTDB, ARIN, RADB 673 100% 70
207.241.196.0/22 No ROA RIR databaseARIN, RADB 673 100% 70
216.185.212.0/22 No ROA RIR databaseALTDB, ARIN, RADB 673 100% 70
38.70.128.0/21 Valid RIR databaseARIN, RADB 673 100% 70

AS-SET

AS394303'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 33 are in fix.csv.

  • ROA: none10
  • Route object: RIR5
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none38.22.240.0/21No ROA covers it. Add a ROA for AS394303, maxLength 21.673 of 673
Route object: RIR38.22.240.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.58.224.0/21No ROA covers it. Add a ROA for AS394303, maxLength 21.673 of 673
Route object: RIR38.58.224.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.65.224.0/22No ROA covers it. Add a ROA for AS394303, maxLength 22.673 of 673
Route object: RIR38.65.224.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.12.120.0/21No ROA covers it. Add a ROA for AS394303, maxLength 21.673 of 673
Route object: RIR154.12.120.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.18.240.0/21No ROA covers it. Add a ROA for AS394303, maxLength 21.673 of 673
Route object: RIR154.18.240.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none74.121.204.0/22No ROA covers it. Add a ROA for AS394303, maxLength 22.673 of 673
ROA: none167.253.104.0/22No ROA covers it. Add a ROA for AS394303, maxLength 22.673 of 673
ROA: none198.175.24.0/22No ROA covers it. Add a ROA for AS394303, maxLength 22.673 of 673
ROA: none207.241.196.0/22No ROA covers it. Add a ROA for AS394303, maxLength 22.673 of 673
ROA: none216.185.212.0/22No ROA covers it. Add a ROA for AS394303, maxLength 22.673 of 673

Route objects not announced

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

23.29.132.0/24RADBNo ROA
23.29.145.0/24RADBNo ROA
50.31.30.0/24ARIN, RADBNo ROA
50.31.65.0/24RADBNo ROA
50.31.78.0/24RADBNo ROA
50.31.98.0/23RADBNo ROA
50.31.114.0/24RADBNo ROA
50.31.116.0/24RADBNo ROA
50.31.119.0/24RADBNo ROA
50.31.252.0/22ARINValid
67.202.70.0/24RADBNo ROA
69.162.134.0/24RADBNo ROA
69.162.173.0/24RADBNo ROA
154.18.247.0/24RADBNo ROA
208.100.53.0/24RADBNo ROA
208.117.4.0/24RADBNo ROA
208.117.38.0/24RADBNo ROA
2605:fbc0::/32ALTDBNo 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.