bgpreport

Network · data from 2026-11-12

AS29436 ASN-IMPERIAL Buryanov Konstantin Volodimirovich

Registry name: ASN-IMPERIAL Buryanov Konstantin Volodimirovich, UA · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
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 AS29436, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29436, 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.
2001:678:1154::/48 No ROA RIR databaseRIPE 635 100% 69
94.240.136.0/21 Valid RIR databaseRIPE 671 100% 68
94.240.160.0/19 Valid RIR databaseRIPE 671 100% 68
192.162.80.0/22 Valid RIR databaseRIPE 671 100% 68
192.166.112.0/23 Valid RIR databaseRIPE 671 100% 68
193.238.36.0/22 Valid RIR databaseRIPE 671 100% 68
195.149.108.0/24 Valid RIR databaseRIPE 671 100% 68
2001:67c:2d9c::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS29436 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: none2001:678:1154::/48No ROA covers it. Add a ROA for AS29436, maxLength 48.635 of 636

Route objects not announced

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