bgpreport

Network · data from 2026-11-12

AS45029 IXDNS Sankt-Peterburg

Registry name: RIPN-SU-NET Join-stock company "Internet Exchange"MSK-IX", RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45029, 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.
193.232.175.0/24 No ROA RIR databaseRIPE 672 100% 66
193.232.188.0/24 No ROA RIR databaseRIPE 672 100% 66
193.232.132.0/24 Valid RIR databaseRIPE 673 100% 66
195.209.18.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.166.0/24 Valid RIR databaseRIPE 672 100% 66
2001:67c:1210::/48 Valid RIR databaseRIPE 636 100% 68
2001:6d0:6d0b::/48 Valid RIR databaseRIPE 636 100% 67
2a0c:a9c7:166::/48 Valid RIR databaseRIPE 636 100% 68

AS-SET

AS45029'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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none193.232.175.0/24No ROA covers it. Add a ROA for AS45029, maxLength 24.672 of 673
ROA: none193.232.188.0/24No ROA covers it. Add a ROA for AS45029, maxLength 24.672 of 673

Route objects not announced

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