bgpreport

Network · data from 2026-11-12

AS54864 ROCKTENN - Rock-Tenn Company

Registry name: ROCKTENN - Rock-Tenn Company, US · not in PeeringDB

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

Announced routes

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

162.34.240.0/20 No ROA None 672 100% 67
204.80.132.0/24 No ROA Other origin only 670 100% 67
142.215.224.64/26 No ROA None 1 0%low visibility 1
162.34.184.0/24 No ROA Other IRR onlyRADB 670 100% 67
162.34.188.0/22 No ROA Other IRR onlyRADB 670 100% 67
162.34.238.0/24 No ROA Other IRR onlyRADB 670 100% 67
162.34.176.0/24 No ROA RIR databaseARIN 672 100% 66
162.34.177.0/24 No ROA RIR databaseARIN 672 100% 66
162.34.254.0/24 No ROA RIR databaseARIN 672 100% 66
162.34.179.0/24 No ROA RIR databaseARIN, RADB 670 100% 67
162.34.252.0/24 No ROA RIR databaseARIN 670 100% 67
162.34.178.0/24 No ROA RIR databaseARIN, RADB 668 99% 67

AS-SET

AS54864 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 20 are in fix.csv.

  • ROA: none12
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none162.34.240.0/20No ROA covers it. Add a ROA for AS54864, maxLength 20.672 of 673
Route object: none162.34.240.0/20No route object for it. Add a route object with origin AS54864 in the RIR database for the space.672 of 673
ROA: none204.80.132.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.670 of 673
Route object: none204.80.132.0/24Route objects for it name AS16900. Add a route object with origin AS54864 in the RIR database for the space.670 of 673
ROA: none142.215.224.64/26No ROA covers it. Add a ROA for AS54864, maxLength 26.1 of 673
Route object: none142.215.224.64/26No route object for it. Add a route object with origin AS54864 in the RIR database for the space.1 of 673
ROA: none162.34.184.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.670 of 673
Route object: RIR162.34.184.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none162.34.188.0/22No ROA covers it. Add a ROA for AS54864, maxLength 22.670 of 673
Route object: RIR162.34.188.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none162.34.238.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.670 of 673
Route object: RIR162.34.238.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none162.34.176.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.672 of 673
ROA: none162.34.177.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.672 of 673
ROA: none162.34.254.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.672 of 673
ROA: none162.34.179.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.670 of 673
ROA: none162.34.252.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.670 of 673
ROA: none162.34.178.0/24No ROA covers it. Add a ROA for AS54864, maxLength 24.668 of 673

Route objects not announced

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

162.34.251.0/24RADBNo ROA
162.34.253.0/24ARINNo 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.