Network · data from 2026-11-12
AS197646 ROOTWEB-AS Rootweb Limited
Registry name: ROOTWEB-AS Rootweb Limited, CY · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197646, 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.
| 80.174.160.0/24 | Invalid: origin | None | 14 2%low visibility |
| 80.174.161.0/24 | Invalid: origin | None | 14 2%low visibility |
| 80.174.162.0/24 | Invalid: origin | None | 14 2%low visibility |
| 80.174.163.0/24 | Invalid: origin | None | 14 2%low visibility |
| 45.6.44.0/24 | Invalid: origin | None | 2 0%low visibility |
| 206.15.48.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 206.15.49.0/24 | Invalid: origin | None | 2 0%low visibility |
| 45.137.84.0/24 | No ROA | None | 2 0%low visibility |
| 211.149.32.0/24 | Valid | RIR databaseAPNIC | 3 0%low visibility |
| 211.149.33.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 211.149.34.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 211.149.35.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS197646 isn't in PeeringDB, where networks name their 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 35 are in fix.csv.
- ROA: origin7
- ROA: none1
- Route object: none8
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 80.174.160.0/24 | ROAs covering it name AS29119, not AS197646. If AS197646 should announce it, add a ROA for AS197646. |
| Route object: none | 80.174.160.0/24 | No route object for it. Add a route object with origin AS197646 in the RIR database for the space. |
| ROA: origin | 80.174.161.0/24 | ROAs covering it name AS29119, not AS197646. If AS197646 should announce it, add a ROA for AS197646. |
| Route object: none | 80.174.161.0/24 | No route object for it. Add a route object with origin AS197646 in the RIR database for the space. |
| ROA: origin | 80.174.162.0/24 | ROAs covering it name AS29119, not AS197646. If AS197646 should announce it, add a ROA for AS197646. |
| Route object: none | 80.174.162.0/24 | No route object for it. Add a route object with origin AS197646 in the RIR database for the space. |
| ROA: origin | 80.174.163.0/24 | ROAs covering it name AS29119, not AS197646. If AS197646 should announce it, add a ROA for AS197646. |
| Route object: none | 80.174.163.0/24 | No route object for it. Add a route object with origin AS197646 in the RIR database for the space. |
| ROA: origin | 45.6.44.0/24 | ROAs covering it name AS29119, not AS197646. If AS197646 should announce it, add a ROA for AS197646. |
| Route object: none | 45.6.44.0/24 | No route object for it. Add a route object with origin AS197646 in the RIR database for the space. |
| ROA: origin | 206.15.48.0/24 | ROAs covering it name AS218949, not AS197646. If AS197646 should announce it, add a ROA for AS197646. |
| Route object: none | 206.15.48.0/24 | Route objects for it name AS218949. Add a route object with origin AS197646 in the RIR database for the space. |
| ROA: origin | 206.15.49.0/24 | ROAs covering it name AS213705, not AS197646. If AS197646 should announce it, add a ROA for AS197646. |
| Route object: none | 206.15.49.0/24 | No route object for it. Add a route object with origin AS197646 in the RIR database for the space. |
| ROA: none | 45.137.84.0/24 | No ROA covers it. Add a ROA for AS197646, maxLength 24. |
| Route object: none | 45.137.84.0/24 | No route object for it. Add a route object with origin AS197646 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS197646 whose prefix no peer sees AS197646 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 87.85.66.0/23 | RADB, RIPE | Valid |
| 87.85.66.0/24 | RIPE | Valid |
| 87.85.67.0/24 | RIPE | Valid |
| 154.83.212.0/24 | AFRINIC | Invalid: origin |
| 154.83.213.0/24 | AFRINIC | Invalid: origin |
| 154.83.214.0/24 | AFRINIC | Invalid: origin |
| 154.83.215.0/24 | AFRINIC | Invalid: origin |
| 194.77.208.0/24 | RIPE | Invalid: origin |
| 194.77.209.0/24 | RIPE | Invalid: origin |
| 194.77.210.0/24 | RIPE | Invalid: origin |
| 194.77.211.0/24 | RIPE | Invalid: origin |
| 194.77.212.0/24 | RIPE | Invalid: origin |
| 194.77.213.0/24 | RIPE | Invalid: origin |
| 194.77.214.0/24 | RIPE | Invalid: origin |
| 194.77.215.0/24 | RIPE | Invalid: origin |
| 212.189.64.0/23 | RADB | Valid |
| 212.189.64.0/24 | RIPE | Valid |
| 212.189.65.0/24 | RIPE | Valid |
| 2a13:b487:4e00::/40 | ALTDB | Invalid: origin |
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.