Announced routes
Every prefix a peer of the route collectors sees with origin AS42156, 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.83.172.0/23 | Valid | Nonecovered by 45.83.172.0/22 | 673 100% |
| 2a0e:e2c4::/32 | Valid | Nonecovered by 2a0e:e2c0::/29 | 634 100% |
| 45.83.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.143.62.0/23 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 69.48.159.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.107.247.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.83.174.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.83.175.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.143.60.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.143.61.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.251.180.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.161.188.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a0e:e2c1::/32 | Valid | RIR databaseRADB, RIPE | 636 100% |
| 2a0e:8480::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0e:e2c0::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0e:e2c2::/32 | Valid | RIR databaseRIPE | 319 50% |
AS-SET
PeeringDB's irr_as_set for AS42156: AS-GNX. 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 (AS42156 isn't in the set, or no route object for AS42156 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 | AS42156 in it | Not covered |
|---|---|---|---|---|---|
| AS-GNX | RIPElists itself further down1 member set in no database: AS197814:AS-BITTNER | 113 | 24 | 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 5 are in fix.csv.
- Route object: none2
- AS-SET: missing member1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.83.172.0/23 | No route object for it. A route object for 45.83.172.0/22 with origin AS42156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42156 in the RIR database for the space. |
| Route object: none | 2a0e:e2c4::/32 | No route object for it. A route object for 2a0e:e2c0::/29 with origin AS42156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42156 in the RIR database for the space. |
| AS-SET: missing member | AS-GNX | AS-GNX (RIPE) lists AS197814:AS-BITTNER; no IRR database read has it. |
Route objects not announced
Route objects with origin AS42156 whose prefix no peer sees AS42156 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 86.106.26.0/24 | RIPE | Invalid: origin |
| 188.241.84.0/24 | 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.