bgpreport

Network · data from 2026-11-12

AS203498 MSA-AS JSC Intellin

Registry name: MSA-AS JSC Intellin, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203498, 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.
2a0c:5640::/32 Valid Nonecovered by 2a0c:5640::/29 635 100% 67
2a0c:5641::/32 Valid Nonecovered by 2a0c:5640::/29 635 100% 67
2a0c:5642::/32 Valid Nonecovered by 2a0c:5640::/29 635 100% 67
2a0c:5643::/32 Valid Nonecovered by 2a0c:5640::/29 635 100% 67
2a0c:5644::/32 Valid Nonecovered by 2a0c:5640::/29 635 100% 67
2a0c:5645::/32 Valid Nonecovered by 2a0c:5640::/29 635 100% 67
2a0c:5646::/32 Valid Nonecovered by 2a0c:5640::/29 635 100% 67
2a0c:5647::/32 Valid Nonecovered by 2a0c:5640::/29 635 100% 67
185.254.212.0/24 Valid RIR databaseRIPE 673 100% 67
185.254.213.0/24 Valid RIR databaseRIPE 673 100% 67
185.254.214.0/24 Valid RIR databaseRIPE 673 100% 67
185.254.215.0/24 Valid RIR databaseRIPE 673 100% 66
185.254.212.0/22 Valid RIR databaseRIPE 672 100% 66
2a0c:5640::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS203498 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 8 are in fix.csv.

  • Route object: none8
ChangePrefix or setDetailFull-table peers
Route object: none2a0c:5640::/32No route object for it. A route object for 2a0c:5640::/29 with origin AS203498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203498 in the RIR database for the space.635 of 636
Route object: none2a0c:5641::/32No route object for it. A route object for 2a0c:5640::/29 with origin AS203498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203498 in the RIR database for the space.635 of 636
Route object: none2a0c:5642::/32No route object for it. A route object for 2a0c:5640::/29 with origin AS203498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203498 in the RIR database for the space.635 of 636
Route object: none2a0c:5643::/32No route object for it. A route object for 2a0c:5640::/29 with origin AS203498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203498 in the RIR database for the space.635 of 636
Route object: none2a0c:5644::/32No route object for it. A route object for 2a0c:5640::/29 with origin AS203498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203498 in the RIR database for the space.635 of 636
Route object: none2a0c:5645::/32No route object for it. A route object for 2a0c:5640::/29 with origin AS203498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203498 in the RIR database for the space.635 of 636
Route object: none2a0c:5646::/32No route object for it. A route object for 2a0c:5640::/29 with origin AS203498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203498 in the RIR database for the space.635 of 636
Route object: none2a0c:5647::/32No route object for it. A route object for 2a0c:5640::/29 with origin AS203498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203498 in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS203498 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.