Network · data from 2026-11-12
AS56718 Redshelf Ltd
Registry name: INTOUCH-BROADBAND Redshelf Ltd, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56718, 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.
| 82.129.13.0/24 | No ROA | None | 673 100% |
| 213.146.162.0/24 | No ROA | None | 673 100% |
| 5.252.37.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.252.38.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 192.166.137.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 192.166.138.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 2a05:9780::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a05:9786::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a05:9787::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a0f:cac0:6::/47 | Valid | RIR databaseRIPE | 635 100% |
| 82.163.164.0/23 | Valid | RIR databaseRIPE | 381 57% |
| 82.163.166.0/23 | Valid | RIR databaseRIPE | 381 57% |
| 185.83.12.0/23 | Valid | RIR databaseRIPE | 381 57% |
| 185.83.14.0/23 | Valid | RIR databaseRIPE | 381 57% |
AS-SET
PeeringDB's irr_as_set for AS56718: AS56718:AS-REDSHELF. 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 (AS56718 isn't in the set, or no route object for AS56718 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 | AS56718 in it | Not covered |
|---|---|---|---|---|---|
| AS56718:AS-REDSHELF | RIPE | 1 | 1 | Yes | 2 |
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: none2
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 82.129.13.0/24 | No ROA covers it. Add a ROA for AS56718, maxLength 24. |
| Route object: none | 82.129.13.0/24 | No route object for it. Add a route object with origin AS56718 in the RIR database for the space. |
| ROA: none | 213.146.162.0/24 | No ROA covers it. Add a ROA for AS56718, maxLength 24. |
| Route object: none | 213.146.162.0/24 | No route object for it. Add a route object with origin AS56718 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56718 whose prefix no peer sees AS56718 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:61a::/48 | ARIN | Valid |
| 2a05:9780::/40 | RIPE | Valid |
| 2a05:9780:200::/40 | RIPE | Valid |
| 2a0f:cac0::/49 | RIPE | Valid |
| 2a0f:cac0:0:8000::/49 | 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.