Network · data from 2026-11-12
AS51906 recast IT GmbH & Co. KG
Registry name: RECAST-AS recast IT GmbH & Co. KG, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51906, 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.
| 31.204.115.0/24 | Valid | Nonecovered by 31.204.112.0/20 | 669 99% |
| 79.171.63.0/24 | Valid | Nonecovered by 79.171.56.0/21 | 669 99% |
| 91.106.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 31.204.112.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 37.130.128.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 37.130.139.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.130.143.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 79.171.56.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 82.197.132.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 91.106.0.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 146.66.224.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 176.241.160.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 79.171.60.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 2001:7f0:101::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:7380::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:7380:400::/39 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS51906: AS-RECAST. 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 (AS51906 isn't in the set, or no route object for AS51906 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 | AS51906 in it | Not covered |
|---|---|---|---|---|---|
| AS-RECAST | 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 9 are in fix.csv.
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 31.204.115.0/24 | No route object for it. A route object for 31.204.112.0/20 with origin AS51906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51906 in the RIR database for the space. |
| Route object: none | 79.171.63.0/24 | No route object for it. A route object for 79.171.56.0/21 with origin AS51906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51906 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51906 whose prefix no peer sees AS51906 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.204.124.0/22 | RIPE | Valid |
| 37.130.140.0/22 | RIPE | Valid |
| 79.171.58.0/24 | RIPE | Valid |
| 146.66.226.0/24 | RIPE | Valid |
| 146.66.227.0/24 | RIPE | Valid |
| 185.2.120.0/22 | RIPE | Valid |
| 185.2.122.0/24 | 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.