bgpreport

Network · data from 2026-11-12

AS394265 BOX-CORP - Box.com

Registry name: BOX-CORP - Box.com, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394265, 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.
2620:117:b402::/48 No ROA Nonecovered by 2620:117:b000::/37 636 100% 67
8.39.49.0/24 No ROA Other IRR onlyRADB 673 100% 67
63.210.208.0/24 No ROA Other IRR onlyRADB 673 100% 67
8.2.225.0/24 No ROA Other IRR onlyRADB 672 100% 67
217.163.22.0/24 No ROA RIR databaseRADB, RIPE 672 100% 66
117.104.145.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
80.169.19.0/24 Valid RIR databaseRADB, RIPE 669 99% 67

AS-SET

AS394265 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2620:117:b402::/48No ROA covers it. Add a ROA for AS394265, maxLength 48.636 of 636
Route object: none2620:117:b402::/48No route object for it. A route object for 2620:117:b000::/37 with origin AS394265 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394265 in the RIR database for the space.636 of 636
ROA: none8.39.49.0/24No ROA covers it. Add a ROA for AS394265, maxLength 24.673 of 673
Route object: RIR8.39.49.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none63.210.208.0/24No ROA covers it. Add a ROA for AS394265, maxLength 24.673 of 673
Route object: RIR63.210.208.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none8.2.225.0/24No ROA covers it. Add a ROA for AS394265, maxLength 24.672 of 673
Route object: RIR8.2.225.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none217.163.22.0/24No ROA covers it. Add a ROA for AS394265, maxLength 24.672 of 673
Route object: RIR117.104.145.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

2620:117:b000::/37RADBNo 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.