Network · data from 2026-11-12
AS48596 InterNetworX Management GmbH
Registry name: INWX InterNetworX Management GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48596, 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.
| 45.87.156.0/23 | Valid | Other origin onlycovered by 45.87.156.0/22 | 548 81% |
| 45.87.156.0/24 | Valid | Other origin onlycovered by 45.87.156.0/22 | 1 0%low visibility |
| 45.87.158.0/24 | Valid | Other origin onlycovered by 45.87.158.0/23 | 1 0%low visibility |
| 45.87.158.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.181.104.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 2a0a:c986:be01::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0a:c986:be02::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a02:d500::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a0a:c980::/29 | Valid | RIR databaseRIPE | 635 100% |
| 45.87.157.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 185.181.104.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 185.181.105.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 185.181.106.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 185.181.107.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS48596: AS-INWX. 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 (AS48596 isn't in the set, or no route object for AS48596 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 | AS48596 in it | Not covered |
|---|---|---|---|---|---|
| AS-INWX | RIPE | 2 | 1 | Yes | 0 |
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 4 are in fix.csv.
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.87.156.0/23 | Route objects for it name AS34997. A route object for 45.87.156.0/22 with origin AS48596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48596 in the RIR database for the space. |
| Route object: none | 45.87.156.0/24 | Route objects for it name AS3223, AS34997. A route object for 45.87.156.0/22 with origin AS48596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48596 in the RIR database for the space. |
| Route object: none | 45.87.158.0/24 | Route objects for it name AS3223, AS34997. A route object for 45.87.158.0/23 with origin AS48596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48596 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48596 whose prefix no peer sees AS48596 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.87.156.0/22 | RIPE | Valid |
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.