bgpreport

Network · data from 2026-11-12

AS46290 MTSAC - MtSAC

Registry name: MTSAC - MtSAC, US · not in PeeringDB

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

Announced routes

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

140.144.126.0/24 No ROA Nonecovered by 140.144.0.0/17 669 99% 68
140.144.126.0/25 No ROA Nonecovered by 140.144.0.0/17 1 0%low visibility 1
140.144.126.128/25 No ROA Nonecovered by 140.144.0.0/17 1 0%low visibility 1
140.144.128.0/25 No ROA Nonecovered by 140.144.128.0/17 1 0%low visibility 1
140.144.128.128/25 No ROA Nonecovered by 140.144.128.0/17 1 0%low visibility 1
140.144.0.0/16 No ROA Other IRR onlyRADB 669 99% 68
140.144.0.0/17 No ROA Other IRR onlyRADB 669 99% 68
140.144.128.0/17 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS46290 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none5
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none140.144.126.0/24No ROA covers it. Add a ROA for AS46290, maxLength 24.669 of 673
Route object: none140.144.126.0/24No route object for it. A route object for 140.144.0.0/17 with origin AS46290 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46290 in the RIR database for the space.669 of 673
ROA: none140.144.126.0/25No ROA covers it. Add a ROA for AS46290, maxLength 25.1 of 673
Route object: none140.144.126.0/25No route object for it. A route object for 140.144.0.0/17 with origin AS46290 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46290 in the RIR database for the space.1 of 673
ROA: none140.144.126.128/25No ROA covers it. Add a ROA for AS46290, maxLength 25.1 of 673
Route object: none140.144.126.128/25No route object for it. A route object for 140.144.0.0/17 with origin AS46290 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46290 in the RIR database for the space.1 of 673
ROA: none140.144.128.0/25No ROA covers it. Add a ROA for AS46290, maxLength 25.1 of 673
Route object: none140.144.128.0/25No route object for it. A route object for 140.144.128.0/17 with origin AS46290 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46290 in the RIR database for the space.1 of 673
ROA: none140.144.128.128/25No ROA covers it. Add a ROA for AS46290, maxLength 25.1 of 673
Route object: none140.144.128.128/25No route object for it. A route object for 140.144.128.0/17 with origin AS46290 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS46290 in the RIR database for the space.1 of 673
ROA: none140.144.0.0/16No ROA covers it. Add a ROA for AS46290, maxLength 16.669 of 673
Route object: RIR140.144.0.0/16Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none140.144.0.0/17No ROA covers it. Add a ROA for AS46290, maxLength 17.669 of 673
Route object: RIR140.144.0.0/17Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none140.144.128.0/17No ROA covers it. Add a ROA for AS46290, maxLength 17.669 of 673
Route object: RIR140.144.128.0/17Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS46290 is announced.

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.