bgpreport

Network · data from 2026-11-12

AS20743 SWX SIX Swiss Exchange AG

Registry name: SWX SIX Swiss Exchange AG, CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20743, 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.
2a01:4642:c800::/40 No ROA Other origin only 633 100% 67
146.109.153.0/24 Valid RIR databaseRIPE 671 100% 67
146.109.160.0/19 Valid RIR databaseRIPE 671 100% 67
146.109.145.0/24 Valid RIR databaseRIPE 669 99% 67
146.109.161.0/24 Valid RIR databaseRIPE 669 99% 67
2a01:4642:100::/40 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS20743 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 23 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none2a01:4642:c800::/40No ROA covers it. Add a ROA for AS20743, maxLength 40.633 of 636
Route object: none2a01:4642:c800::/40Route objects for it name AS9042, AS19905. Add a route object with origin AS20743 in the RIR database for the space.633 of 636

Route objects not announced

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

146.109.0.0/24RIPEInvalid: origin
146.109.1.0/24RIPEInvalid: origin
146.109.2.0/24RIPEInvalid: origin
146.109.3.0/24RIPEInvalid: origin
146.109.4.0/23RIPEInvalid: origin
146.109.4.0/24RIPEInvalid: origin
146.109.6.0/23RIPEInvalid: origin
146.109.6.0/24RIPEInvalid: origin
146.109.64.0/24RIPEInvalid: origin
146.109.65.0/24RIPEInvalid: origin
146.109.66.0/24RIPEInvalid: origin
146.109.67.0/24RIPEInvalid: origin
146.109.68.0/23RIPEInvalid: origin
146.109.68.0/24RIPEInvalid: origin
146.109.69.0/24RIPEInvalid: origin
146.109.70.0/23RIPEInvalid: origin
146.109.70.0/24RIPEInvalid: origin
146.109.128.0/24RIPEInvalid: origin
146.109.129.0/24RIPEInvalid: origin
146.109.224.0/19RIPEInvalid: origin
2a01:4642:200::/40RIPEValid

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.