Network · data from 2026-11-12
AS62163 IP River Limited
Registry name: IPRIVER-AS IP River Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62163, 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.
| 194.40.246.0/23 | Valid | None | 673 100% |
| 5.157.64.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 46.161.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.161.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.161.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 154.47.66.0/24 | Valid | RIR databaseARIN | 673 100% |
| 185.99.164.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.99.165.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.99.166.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.99.167.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.113.68.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.113.80.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.249.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.37.80.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.56.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.104.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.146.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.185.92.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 46.161.217.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 154.47.82.0/24 | Valid | RIR databaseARIN | 672 100% |
| 154.47.84.0/24 | Valid | RIR databaseARIN | 672 100% |
| 154.47.86.0/24 | Valid | RIR databaseARIN | 672 100% |
| 154.47.89.0/24 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS62163's PeeringDB record names no AS-SET.
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 10 are in fix.csv.
- Route object: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 194.40.246.0/23 | No route object for it. Add a route object with origin AS62163 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62163 whose prefix no peer sees AS62163 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.157.64.0/24 | RIPE | Invalid: maxLength |
| 5.157.65.0/24 | RIPE | Invalid: maxLength |
| 5.157.70.0/24 | RIPE | Invalid: maxLength |
| 5.157.71.0/24 | RIPE | Invalid: maxLength |
| 136.238.195.0/24 | ARIN, NTTCOM | No ROA |
| 194.40.246.0/24 | RIPE | Valid |
| 194.40.247.0/24 | RIPE | Valid |
| 195.60.86.0/24 | RIPE | Invalid: origin |
| 2a06:3f00::/29 | 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.