Network · data from 2026-11-12
AS44133 IPAX Internet Services
Registry name: IPAX-AS IPAX GmbH, AT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44133, 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.
| 185.237.94.0/24 | Invalid: origin | None | 4 1%low visibility |
| 45.144.208.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 2a0f:8000::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 37.252.184.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.39.64.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.189.24.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 104.252.152.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.253.180.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 104.253.196.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 185.119.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 205.188.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.38.113.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.38.114.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.38.115.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.76.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 45.39.96.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 2a00:63c0::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS44133: RIPE::AS-IPAX-TRANSIT-V4. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS44133 isn't in the set, or no route object for AS44133 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS44133 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-IPAX-TRANSIT-V4 | RIPE | 3 | 1 | Yes | 1 |
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 9 are in fix.csv.
- ROA: origin1
- ROA: none2
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.237.94.0/24 | ROAs covering it name AS15731, not AS44133. If AS44133 should announce it, add a ROA for AS44133. |
| Route object: none | 185.237.94.0/24 | No route object for it. Add a route object with origin AS44133 in the RIR database for the space. |
| ROA: none | 45.144.208.0/23 | No ROA covers it. Add a ROA for AS44133, maxLength 23. |
| ROA: none | 2a0f:8000::/29 | No ROA covers it. Add a ROA for AS44133, maxLength 29. |
Route objects not announced
Route objects with origin AS44133 whose prefix no peer sees AS44133 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.252.184.0/22 | RIPE | Invalid: maxLength |
| 37.252.188.0/22 | RIPE | Invalid: maxLength |
| 45.144.208.0/22 | RIPE | No ROA |
| 93.189.24.0/22 | RIPE | Invalid: maxLength |
| 93.189.28.0/22 | 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.