Network · data from 2026-11-12
AS61460 AS61460 - NETLAND CHILE S.A.
Registry name: AS61460 - NETLAND CHILE S.A., CL · not in PeeringDB
16IPv4 routes
100.0% RPKI valid · 50.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
8 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS61460, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS61460, 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.
| 201.217.248.0/24 | Valid | Nonecovered by 201.217.248.0/21 | 672 100% |
| 201.217.249.0/24 | Valid | Nonecovered by 201.217.248.0/21 | 672 100% |
| 201.217.250.0/24 | Valid | Nonecovered by 201.217.248.0/21 | 672 100% |
| 201.217.251.0/24 | Valid | Nonecovered by 201.217.248.0/21 | 672 100% |
| 201.217.252.0/24 | Valid | Nonecovered by 201.217.248.0/21 | 672 100% |
| 201.217.253.0/24 | Valid | Nonecovered by 201.217.248.0/21 | 672 100% |
| 201.217.254.0/24 | Valid | Nonecovered by 201.217.248.0/21 | 672 100% |
| 201.217.255.0/24 | Valid | Nonecovered by 201.217.248.0/21 | 672 100% |
| 161.0.184.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 161.0.185.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 161.0.186.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 161.0.187.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 161.0.188.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 161.0.189.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 161.0.190.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 161.0.191.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
AS-SET
AS61460 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 22 are in fix.csv.
- Route object: none8
- Route object: RIR8
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 201.217.248.0/24 | No route object for it. A route object for 201.217.248.0/21 with origin AS61460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61460 in the RIR database for the space. |
| Route object: none | 201.217.249.0/24 | No route object for it. A route object for 201.217.248.0/21 with origin AS61460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61460 in the RIR database for the space. |
| Route object: none | 201.217.250.0/24 | No route object for it. A route object for 201.217.248.0/21 with origin AS61460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61460 in the RIR database for the space. |
| Route object: none | 201.217.251.0/24 | No route object for it. A route object for 201.217.248.0/21 with origin AS61460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61460 in the RIR database for the space. |
| Route object: none | 201.217.252.0/24 | No route object for it. A route object for 201.217.248.0/21 with origin AS61460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61460 in the RIR database for the space. |
| Route object: none | 201.217.253.0/24 | No route object for it. A route object for 201.217.248.0/21 with origin AS61460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61460 in the RIR database for the space. |
| Route object: none | 201.217.254.0/24 | No route object for it. A route object for 201.217.248.0/21 with origin AS61460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61460 in the RIR database for the space. |
| Route object: none | 201.217.255.0/24 | No route object for it. A route object for 201.217.248.0/21 with origin AS61460 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61460 in the RIR database for the space. |
| Route object: RIR | 161.0.184.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 161.0.185.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 161.0.186.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 161.0.187.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 161.0.188.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 161.0.189.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 161.0.190.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 161.0.191.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61460 whose prefix no peer sees AS61460 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 161.0.184.0/21 | ALTDB, NTTCOM | Valid |
| 161.0.184.0/23 | NTTCOM | Valid |
| 161.0.186.0/23 | NTTCOM | Valid |
| 161.0.188.0/23 | NTTCOM | Valid |
| 161.0.190.0/23 | NTTCOM | Valid |
| 201.217.248.0/21 | ALTDB, NTTCOM | 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.