bgpreport

Network · data from 2026-11-12

AS210616 SIBMEDVED-AS SM Ltd.

Registry name: SIBMEDVED-AS SM Ltd., RU · not in PeeringDB

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

Announced routes

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

146.158.104.0/24 Valid Nonecovered by 146.158.104.0/23 673 100% 66
146.158.112.0/23 Valid Nonecovered by 146.158.112.0/22 673 100% 66
146.158.108.0/23 Valid Nonecovered by 146.158.96.0/19 672 100% 66
93.171.184.0/24 Valid RIR databaseRIPE 673 100% 67
93.171.185.0/24 Valid RIR databaseRIPE 673 100% 66
93.171.186.0/23 Valid RIR databaseRIPE 673 100% 66
146.120.53.0/24 Valid RIR databaseRIPE 673 100% 66
146.120.54.0/24 Valid RIR databaseRIPE 673 100% 66
146.120.55.0/24 Valid RIR databaseRIPE 673 100% 66
146.120.116.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.88.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.90.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.91.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.96.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.97.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.98.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.98.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.100.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.100.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.101.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.102.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.105.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.106.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.106.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.107.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.108.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.109.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.110.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.111.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.113.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.114.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.114.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.116.0/22 Valid RIR databaseRIPE 673 100% 66
146.158.118.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.120.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.120.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.122.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.123.0/24 Valid RIR databaseRIPE 673 100% 66
146.158.124.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.126.0/23 Valid RIR databaseRIPE 673 100% 66
212.15.56.0/23 Valid RIR databaseRIPE 673 100% 66
212.15.58.0/23 Valid RIR databaseRIPE 673 100% 66
212.15.58.0/24 Valid RIR databaseRIPE 673 100% 66
212.15.62.0/24 Valid RIR databaseRIPE 673 100% 66
212.15.63.0/24 Valid RIR databaseRIPE 673 100% 66
146.120.52.0/24 Valid RIR databaseRIPE 672 100% 67
146.120.117.0/24 Valid RIR databaseRIPE 672 100% 67
146.158.115.0/24 Valid RIR databaseRIPE 672 100% 66
146.158.126.0/24 Valid RIR databaseRIPE 672 100% 66
146.158.127.0/24 Valid RIR databaseRIPE 672 100% 66
212.15.56.0/24 Valid RIR databaseRIPE 671 100% 66
212.15.57.0/24 Valid RIR databaseRIPE 671 100% 66
212.15.59.0/24 Valid RIR databaseRIPE 671 100% 66
212.15.61.0/24 Valid RIR databaseRIPE 671 100% 66
93.171.186.0/24 Valid RIR databaseRIPE 3 0%low visibility 2
93.171.187.0/24 Valid RIR databaseRIPE 3 0%low visibility 2
146.158.99.0/24 Valid RIR databaseRIPE 3 0%low visibility 2
146.158.116.0/24 Valid RIR databaseRIPE 3 0%low visibility 2
146.158.117.0/24 Valid RIR databaseRIPE 3 0%low visibility 2
146.158.118.0/24 Valid RIR databaseRIPE 3 0%low visibility 2
146.158.119.0/24 Valid RIR databaseRIPE 3 0%low visibility 2

AS-SET

AS210616 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 22 are in fix.csv.

  • Route object: none3
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
Route object: none146.158.104.0/24No route object for it. A route object for 146.158.104.0/23 with origin AS210616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210616 in the RIR database for the space.673 of 673
Route object: none146.158.112.0/23No route object for it. A route object for 146.158.112.0/22 with origin AS210616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210616 in the RIR database for the space.673 of 673
Route object: none146.158.108.0/23No route object for it. A route object for 146.158.96.0/19 with origin AS210616 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210616 in the RIR database for the space.672 of 673

Route objects not announced

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

93.171.184.0/22RIPEValid
93.171.213.0/24RIPEValid
146.120.52.0/22RIPEValid
146.120.116.0/23RIPEValid
146.158.88.0/22RIPEValid
146.158.89.0/24RIPEValid
146.158.96.0/19RIPEValid
146.158.104.0/22RIPEValid
146.158.104.0/23RIPEValid
146.158.110.0/24RIPEValid
146.158.112.0/22RIPEValid
146.158.112.0/24RIPEValid
146.158.116.0/23RIPEValid
146.158.121.0/24RIPEValid
146.158.122.0/23RIPEValid
146.158.124.0/24RIPEValid
146.158.125.0/24RIPEValid
212.15.56.0/22RIPEValid
212.15.62.0/23RIPEValid

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.