Network · data from 2026-11-12
AS25038 AIXTRANET-AS Alfred Schruff trading as AIXTRANET
Registry name: AIXTRANET-AS Alfred Schruff trading as AIXTRANET, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25038, 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.
| 194.123.164.0/24 | Invalid: origin | Other origin only | 6 1%low visibility |
| 81.24.32.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 185.216.232.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 193.141.58.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 62.132.115.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.45.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.121.123.0/24 | Valid | RIR databaseRIPE | 199 30% |
AS-SET
AS25038 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 6 are in fix.csv.
- ROA: origin1
- ROA: none3
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 194.123.164.0/24 | ROAs covering it name AS3257, not AS25038. If AS25038 should announce it, add a ROA for AS25038. |
| Route object: none | 194.123.164.0/24 | Route objects for it name AS286, AS3257. Add a route object with origin AS25038 in the RIR database for the space. |
| ROA: none | 81.24.32.0/20 | No ROA covers it. Add a ROA for AS25038, maxLength 20. |
| ROA: none | 185.216.232.0/22 | No ROA covers it. Add a ROA for AS25038, maxLength 22. |
| ROA: none | 193.141.58.0/24 | No ROA covers it. Add a ROA for AS25038, maxLength 24. |
Route objects not announced
Route objects with origin AS25038 whose prefix no peer sees AS25038 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 196.6.211.0/24 | NTTCOM, RADB | No 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.