bgpreport

Network · data from 2026-11-12

AS198130 IPSAL

Registry name: IPSAL Salimov Rustam Khayriddinovich, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198130, 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.
80.173.146.0/24 Invalid: origin None 2 0%low visibility 1
85.28.61.0/24 Valid RIR databaseRIPE 673 100% 67
91.194.55.0/24 Valid RIR databaseRIPE 673 100% 67
93.177.93.0/24 Valid RIR databaseRIPE 673 100% 67
95.181.153.0/24 Valid RIR databaseRIPE 673 100% 67
185.86.6.0/24 Valid RIR databaseRIPE 673 100% 67
185.250.210.0/24 Valid RIR databaseRIPE 673 100% 67
185.221.197.0/24 Valid RIR databaseRIPE 672 100% 67
185.185.232.0/24 Valid RIR databaseRIPE 671 100% 68
193.160.73.0/24 Valid RIR databaseRIPE 671 100% 67
194.28.158.0/24 Valid RIR databaseRIPE 671 100% 67
212.69.132.0/24 Valid RIR databaseRIPE 671 100% 67
45.140.6.0/24 Valid RIR databaseRIPE 655 97% 66
200.163.82.0/24 Valid RIR databaseRIPE 653 97% 67
200.163.86.0/24 Valid RIR databaseRIPE 653 97% 67

AS-SET

AS198130's PeeringDB record names no 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 5 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin80.173.146.0/24ROAs covering it name AS209372, AS213541, not AS198130. If AS198130 should announce it, add a ROA for AS198130.2 of 673
Route object: none80.173.146.0/24No route object for it. Add a route object with origin AS198130 in the RIR database for the space.2 of 673

Route objects not announced

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

94.187.199.0/24RIPEValid
94.187.200.0/24RIPEValid
94.187.201.0/24RIPEValid

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.