bgpreport

Network · data from 2026-11-12

AS51812 KTVS-AS KTVS Ltd.

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51812, 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.
46.148.58.0/23 Valid Nonecovered by 46.148.48.0/20 2 0%low visibility 2
46.148.48.0/20 Valid RIR databaseRIPE 673 100% 66
92.38.20.0/23 Valid RIR databaseRIPE 673 100% 66
92.38.88.0/23 Valid RIR databaseRIPE 673 100% 66
92.38.90.0/23 Valid RIR databaseRIPE 673 100% 66
92.253.216.0/23 Valid RIR databaseRIPE 673 100% 66
93.170.32.0/23 Valid RIR databaseRIPE 673 100% 66
93.170.50.0/23 Valid RIR databaseRIPE 673 100% 66
93.170.104.0/23 Valid RIR databaseRIPE 673 100% 66
93.170.120.0/23 Valid RIR databaseRIPE 673 100% 66
93.170.138.0/23 Valid RIR databaseRIPE 673 100% 66
93.170.172.0/23 Valid RIR databaseRIPE 673 100% 66
93.171.14.0/23 Valid RIR databaseRIPE 673 100% 66
93.171.98.0/23 Valid RIR databaseRIPE 673 100% 66
93.171.216.0/23 Valid RIR databaseRIPE 673 100% 66
95.46.12.0/23 Valid RIR databaseRIPE 673 100% 66
95.46.14.0/23 Valid RIR databaseRIPE 673 100% 66
95.46.38.0/23 Valid RIR databaseRIPE 673 100% 66
95.46.98.0/23 Valid RIR databaseRIPE 673 100% 66
95.46.152.0/23 Valid RIR databaseRIPE 673 100% 66
95.47.184.0/23 Valid RIR databaseRIPE 673 100% 66
95.47.198.0/23 Valid RIR databaseRIPE 673 100% 66
95.47.202.0/23 Valid RIR databaseRIPE 673 100% 66
146.120.98.0/23 Valid RIR databaseRIPE 673 100% 66
146.120.114.0/23 Valid RIR databaseRIPE 673 100% 66
146.120.156.0/23 Valid RIR databaseRIPE 673 100% 66
146.120.186.0/23 Valid RIR databaseRIPE 673 100% 66
146.158.10.0/23 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS51812 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none46.148.58.0/23No route object for it. A route object for 46.148.48.0/20 with origin AS51812 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51812 in the RIR database for the space.2 of 673

Route objects not announced

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