bgpreport

Network · data from 2026-11-12

AS200463 LETKOM LLC firm "Letkom"

Registry name: LETKOM LLC firm "Letkom", RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200463, 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.
91.230.196.0/23 No ROA RIR databaseRIPE 673 100% 66
193.232.114.0/24 No ROA RIR databaseRIPE 673 100% 66
193.232.245.0/24 No ROA RIR databaseRIPE 673 100% 66
195.19.221.0/24 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS200463 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 4 are in fix.csv.

  • ROA: none4
ChangePrefix or setDetailFull-table peers
ROA: none91.230.196.0/23No ROA covers it. Add a ROA for AS200463, maxLength 23.673 of 673
ROA: none193.232.114.0/24No ROA covers it. Add a ROA for AS200463, maxLength 24.673 of 673
ROA: none193.232.245.0/24No ROA covers it. Add a ROA for AS200463, maxLength 24.673 of 673
ROA: none195.19.221.0/24No ROA covers it. Add a ROA for AS200463, maxLength 24.673 of 673

Route objects not announced

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