bgpreport

Network · data from 2026-11-12

AS213499 LINK-UP-ISP-AS Gorokhov Kirill

Registry name: LINK-UP-ISP-AS Gorokhov Kirill, RU · not in PeeringDB

5IPv4 routes 80.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS213499, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213499, 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.
194.242.6.0/23 No ROA RIR databaseRIPE 673 100% 66
146.158.92.0/23 Valid RIR databaseRIPE 673 100% 66
213.135.80.0/24 Valid RIR databaseRIPE 673 100% 66
194.242.6.0/24 Valid RIR databaseRIPE 138 21% 36
194.242.7.0/24 Valid RIR databaseRIPE 138 21% 36

AS-SET

AS213499 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.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none194.242.6.0/23No ROA covers it. Add a ROA for AS213499, maxLength 23.673 of 673

Route objects not announced

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