bgpreport

Network · data from 2026-11-12

AS30418 SUMT-CMH - SumTotal Systems, Inc.

Registry name: SUMT-CMH - SumTotal Systems, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30418, 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.216.88.0/24 No ROA Other origin onlycovered by 162.216.88.0/21 673 100% 67
162.216.89.0/24 No ROA Other origin onlycovered by 162.216.88.0/21 673 100% 67
162.216.90.0/24 No ROA Other origin onlycovered by 162.216.88.0/21 673 100% 67
199.59.200.0/22 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS30418 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 12 are in fix.csv.

  • ROA: none4
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none162.216.88.0/24No ROA covers it. Add a ROA for AS30418, maxLength 24.673 of 673
Route object: none162.216.88.0/24Route objects for it name AS11320. A route object for 162.216.88.0/21 with origin AS30418 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30418 in the RIR database for the space.673 of 673
ROA: none162.216.89.0/24No ROA covers it. Add a ROA for AS30418, maxLength 24.673 of 673
Route object: none162.216.89.0/24Route objects for it name AS11320. A route object for 162.216.88.0/21 with origin AS30418 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30418 in the RIR database for the space.673 of 673
ROA: none162.216.90.0/24No ROA covers it. Add a ROA for AS30418, maxLength 24.673 of 673
Route object: none162.216.90.0/24Route objects for it name AS11320. A route object for 162.216.88.0/21 with origin AS30418 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30418 in the RIR database for the space.673 of 673
ROA: none199.59.200.0/22No ROA covers it. Add a ROA for AS30418, maxLength 22.673 of 673
Route object: RIR199.59.200.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

162.216.88.0/21RADBNo ROA
162.216.91.0/24RADBNo ROA
162.216.93.0/24RADBNo ROA
162.216.94.0/23RADBNo 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.