Network · data from 2026-11-12
AS44453 internex-as interneX GmbH
Registry name: internex-as interneX GmbH, AT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44453, 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.
| 2a03:3180::/36 | Valid | Nonecovered by 2a03:3180::/32 | 635 100% |
| 2a03:3180:4000::/36 | Valid | Nonecovered by 2a03:3180::/32 | 635 100% |
| 5.132.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.132.161.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.132.162.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 5.132.189.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.132.190.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.198.144.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 128.204.128.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 144.208.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 144.208.128.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.2.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS44453 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 25 are in fix.csv.
- Route object: none2
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a03:3180::/36 | No route object for it. A route object for 2a03:3180::/32 with origin AS44453 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44453 in the RIR database for the space. |
| Route object: none | 2a03:3180:4000::/36 | No route object for it. A route object for 2a03:3180::/32 with origin AS44453 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44453 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44453 whose prefix no peer sees AS44453 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.132.136.0/23 | RIPE | No ROA |
| 5.132.160.0/23 | RIPE | No ROA |
| 5.132.162.0/24 | RIPE | Valid |
| 5.132.190.0/23 | RIPE | No ROA |
| 5.198.146.0/24 | RIPE | Invalid: maxLength |
| 5.198.149.0/24 | RIPE | Invalid: maxLength |
| 5.198.151.0/24 | RIPE | Invalid: maxLength |
| 5.198.154.0/24 | RIPE | Invalid: maxLength |
| 5.198.158.0/24 | RIPE | Invalid: maxLength |
| 128.204.145.0/24 | RIPE | Valid |
| 128.204.148.0/24 | RIPE | Valid |
| 128.204.158.0/24 | RIPE | Valid |
| 128.204.159.0/24 | RIPE | Valid |
| 144.208.4.0/24 | RIPE | Valid |
| 144.208.5.0/24 | RIPE | Valid |
| 144.208.6.0/24 | RIPE | Valid |
| 144.208.7.0/24 | RIPE | Valid |
| 144.208.132.0/22 | RIPE | Valid |
| 185.2.157.0/24 | RIPE | Invalid: maxLength |
| 185.2.158.0/24 | RIPE | Invalid: maxLength |
| 185.2.159.0/24 | RIPE | Invalid: maxLength |
| 2a03:3180::/32 | RIPE | Valid |
| 2a03:3180:e::/48 | RIPE | Invalid: maxLength |
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.