bgpreport

Network · data from 2026-11-12

AS47211 KOLPINONET-AS OOO Kolpinskie Internet-Seti

Registry name: KOLPINONET-AS OOO Kolpinskie Internet-Seti, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47211, 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.
31.133.224.0/19 No ROA RIR databaseRIPE 669 99% 68
109.197.48.0/21 No ROA RIR databaseRIPE 668 99% 68
2a02:2808:1006::/48 No ROA RIR databaseRIPE 635 100% 69

AS-SET

AS47211 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 3 are in fix.csv.

  • ROA: none3
ChangePrefix or setDetailFull-table peers
ROA: none31.133.224.0/19No ROA covers it. Add a ROA for AS47211, maxLength 19.669 of 673
ROA: none109.197.48.0/21No ROA covers it. Add a ROA for AS47211, maxLength 21.668 of 673
ROA: none2a02:2808:1006::/48No ROA covers it. Add a ROA for AS47211, maxLength 48.635 of 636

Route objects not announced

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