bgpreport

Network · data from 2026-11-12

AS51469 Petiak

Registry name: Petiak Petiak System Co JSC, IR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51469, 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.171.216.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
31.171.218.0/23 Valid RIR databaseRIPE 670 100% 66
31.171.220.0/23 Valid RIR databaseRIPE 670 100% 66
31.171.222.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
185.16.232.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
185.16.234.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
217.170.240.0/23 Valid RIR databaseRIPE 670 100% 66
217.170.242.0/23 Valid RIR databaseRIPE 670 100% 66
217.170.244.0/23 Valid RIR databaseRIPE 670 100% 66
217.170.244.0/24 Valid RIR databaseRIPE 670 100% 66
217.170.245.0/24 Valid RIR databaseRIPE 670 100% 66
217.170.246.0/23 Valid RIR databaseRIPE 670 100% 66
217.170.248.0/23 Valid RIR databaseRIPE 670 100% 66
217.170.250.0/23 Valid RIR databaseRIPE 670 100% 66
217.170.252.0/23 Valid RIR databaseRIPE 670 100% 66
217.170.254.0/23 Valid RIR databaseRIPE 670 100% 66
2a00:6380::/32 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS51469's PeeringDB record names no 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 19 are in fix.csv.

  • Route object: not announced19

Route objects not announced

Route objects with origin AS51469 whose prefix no peer sees AS51469 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.160.116.0/22RIPEInvalid: origin
5.160.144.0/23RIPEInvalid: origin
5.202.168.0/21RIPEInvalid: origin
31.171.216.0/21RIPENo ROA
31.171.216.0/22RIPENo ROA
31.171.220.0/22RIPENo ROA
81.31.224.0/22RIPEInvalid: origin
81.31.228.0/23RIPEInvalid: origin
81.31.236.0/22RIPEInvalid: origin
81.31.240.0/23RIPEInvalid: origin
81.31.248.0/23RIPEInvalid: origin
185.16.232.0/22RIPENo ROA
217.170.240.0/20RIPENo ROA
217.170.240.0/21RIPENo ROA
217.170.240.0/22RIPENo ROA
217.170.244.0/22RIPENo ROA
217.170.248.0/21RIPENo ROA
217.170.248.0/22RIPENo ROA
217.170.252.0/22RIPENo ROA

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.