bgpreport

Network · data from 2026-11-12

AS22575 MASSMUTUAL2 - Massachusetts Mutual Life Insurance Company

Registry name: MASSMUTUAL2 - Massachusetts Mutual Life Insurance Company, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22575, 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.
12.189.182.0/23 No ROA Other IRR onlyRADB 672 100% 67
170.6.8.0/21 Valid Other origin onlycovered by 170.6.0.0/19 672 100% 67
170.6.17.0/24 Valid Nonecovered by 170.6.0.0/19 671 100% 67
170.6.16.0/24 Valid Other IRR onlyRADB 672 100% 67
170.6.0.0/21 Valid Other IRR onlyRADB 671 100% 67
170.6.0.0/19 Valid RIR databaseARIN 673 100% 67

AS-SET

AS22575 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 19 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none12.189.182.0/23No ROA covers it. Add a ROA for AS22575, maxLength 23.672 of 673
Route object: RIR12.189.182.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none170.6.8.0/21Route objects for it name AS40740. A route object for 170.6.0.0/19 with origin AS22575 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22575 in the RIR database for the space.672 of 673
Route object: none170.6.17.0/24No route object for it. A route object for 170.6.0.0/19 with origin AS22575 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22575 in the RIR database for the space.671 of 673
Route object: RIR170.6.16.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.6.0.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

63.66.112.0/23RADBNo ROA
63.90.76.0/22RADBNo ROA
63.174.52.0/22RADBNo ROA
63.174.52.0/24RADBNo ROA
63.174.53.0/24RADBNo ROA
63.174.54.0/24RADBNo ROA
63.174.55.0/24RADBNo ROA
64.95.227.0/24RADBNo ROA
65.215.69.0/24RADBNo ROA
65.215.120.0/22RADBNo ROA
170.6.0.0/16RADBNo ROA
170.6.0.0/24RADBValid
170.6.3.0/24RADBValid

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.