bgpreport

Network · data from 2026-11-12

AS43832 IXDNS Moscow

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43832, 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.128.0/23 No ROA RIR databaseRIPE 673 100% 66
194.190.168.0/24 No ROA RIR databaseRIPE 673 100% 66
194.226.75.0/24 No ROA RIR databaseRIPE 673 100% 66
2001:6d0:ffd4::/48 No ROA RIR databaseRIPE 635 100% 68
2001:678:17::/48 No ROA RIR databaseRIPE 633 100% 67
193.232.128.0/24 No ROA RIR databaseRIPE 124 18% 40
2001:678:17::/49 No ROA RIR databaseRIPE 5 1%low visibility 5
62.76.62.0/24 Valid RIR databaseRIPE 673 100% 66
62.76.76.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.93.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.124.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.160.0/24 Valid RIR databaseRIPE 673 100% 66
193.232.177.0/24 Valid RIR databaseRIPE 673 100% 66
194.85.104.0/24 Valid RIR databaseRIPE 673 100% 66
194.85.108.0/24 Valid RIR databaseRIPE 673 100% 66
2001:67c:1442::/48 Valid RIR databaseRIPE 636 100% 68
2001:67c:1444::/48 Valid RIR databaseRIPE 636 100% 67
2001:6d0:d6::/48 Valid RIR databaseRIPE 636 100% 69
2001:6d0:6d0::/48 Valid RIR databaseRIPE 636 100% 69
2001:6d0:ffb9::/48 Valid RIR databaseRIPE 636 100% 67
2001:6d0:fffc::/48 Valid RIR databaseRIPE 636 100% 68
2a0c:a9c7:160::/48 Valid RIR databaseRIPE 636 100% 68
2a0c:a9c7:177::/48 Valid RIR databaseRIPE 636 100% 68

AS-SET

AS43832'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 14 are in fix.csv.

  • ROA: none7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none193.232.128.0/23No ROA covers it. Add a ROA for AS43832, maxLength 23.673 of 673
ROA: none194.190.168.0/24No ROA covers it. Add a ROA for AS43832, maxLength 24.673 of 673
ROA: none194.226.75.0/24No ROA covers it. Add a ROA for AS43832, maxLength 24.673 of 673
ROA: none2001:6d0:ffd4::/48No ROA covers it. Add a ROA for AS43832, maxLength 48.635 of 636
ROA: none2001:678:17::/48No ROA covers it. Add a ROA for AS43832, maxLength 48.633 of 636
ROA: none193.232.128.0/24No ROA covers it. Add a ROA for AS43832, maxLength 24.124 of 673
ROA: none2001:678:17::/49No ROA covers it. Add a ROA for AS43832, maxLength 49.5 of 636

Route objects not announced

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

62.76.62.0/23RIPEValid
62.76.76.0/23RIPEValid
195.209.0.0/24RIPENo ROA
2001:6d0:d6::/49RIPEInvalid: maxLength
2001:6d0:6d0::/49RIPEInvalid: maxLength
2a09:bd00:ffcb::/48RIPENo ROA
2a09:bd00:ffcc::/48RIPENo 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.