bgpreport

Network · data from 2026-11-12

AS25432 INFINEON-AS Infineon Technologies AG

Registry name: INFINEON-AS Infineon Technologies AG, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25432, 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.
217.10.50.0/23 No ROA RIR databaseRIPE 673 100% 66
217.10.52.0/23 No ROA RIR databaseRIPE 673 100% 66
2a00:18f0:1e00::/48 No ROA RIR databaseRIPE 633 100% 67

AS-SET

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

  • ROA: none3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none217.10.50.0/23No ROA covers it. Add a ROA for AS25432, maxLength 23.673 of 673
ROA: none217.10.52.0/23No ROA covers it. Add a ROA for AS25432, maxLength 23.673 of 673
ROA: none2a00:18f0:1e00::/48No ROA covers it. Add a ROA for AS25432, maxLength 48.633 of 636

Route objects not announced

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

217.10.48.0/20RIPENo ROA
217.10.48.0/24RIPENo ROA
217.10.55.0/24RIPENo ROA
217.10.60.0/24RIPENo 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.