bgpreport

Network · data from 2026-11-12

AS59443 BAYNUR-AS Baynur and P Ltd.

Registry name: BAYNUR-AS Baynur and P Ltd., KZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59443, 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.
95.182.0.0/21 No ROA RIR databaseRIPE 673 100% 66
95.182.8.0/21 No ROA RIR databaseRIPE 673 100% 66
95.182.16.0/21 No ROA RIR databaseRIPE 673 100% 66
176.122.80.0/21 No ROA RIR databaseRIPE 673 100% 66
185.31.72.0/23 No ROA RIR databaseRIPE 673 100% 66
185.31.74.0/23 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS59443 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 6 are in fix.csv.

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none95.182.0.0/21No ROA covers it. Add a ROA for AS59443, maxLength 21.673 of 673
ROA: none95.182.8.0/21No ROA covers it. Add a ROA for AS59443, maxLength 21.673 of 673
ROA: none95.182.16.0/21No ROA covers it. Add a ROA for AS59443, maxLength 21.673 of 673
ROA: none176.122.80.0/21No ROA covers it. Add a ROA for AS59443, maxLength 21.673 of 673
ROA: none185.31.72.0/23No ROA covers it. Add a ROA for AS59443, maxLength 23.673 of 673
ROA: none185.31.74.0/23No ROA covers it. Add a ROA for AS59443, maxLength 23.673 of 673

Route objects not announced

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