Network · data from 2026-11-12
AS401146 TURNEL - TURNEL
Registry name: TURNEL - TURNEL, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS401146, 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.
| 103.68.111.0/24 | Invalid: origin | RIR databaseRIPE | 78 12% |
| 2602:f2dc::/44 | No ROA | None | 633 100% |
| 103.204.192.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 31.56.96.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 85.155.227.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS401146 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 6 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.68.111.0/24 | ROAs covering it name AS61138, not AS401146. If AS401146 should announce it, add a ROA for AS401146. |
| ROA: none | 2602:f2dc::/44 | No ROA covers it. Add a ROA for AS401146, maxLength 44. |
| Route object: none | 2602:f2dc::/44 | No route object for it. Add a route object with origin AS401146 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS401146 whose prefix no peer sees AS401146 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.164.244.0/24 | ARIN | Valid |
| 154.198.185.0/24 | AFRINIC | Valid |
| 154.199.7.0/24 | AFRINIC | 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.