Network · data from 2026-11-12
AS16874 SONDA - DC Teatinos
Registry name: AS16874 - SONDA S.A., CL · PeeringDB
20IPv4 routes
80.0% RPKI valid · 70.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
4No ROA
6 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS16874, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS16874, 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.
| 200.1.128.0/24 | No ROA | Other origin only | 671 100% |
| 192.231.110.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 200.0.156.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 200.2.75.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 198.41.41.0/24 | Valid | Nonecovered by 198.41.40.0/22 | 673 100% |
| 198.41.40.0/24 | Valid | Nonecovered by 198.41.40.0/22 | 672 100% |
| 200.0.158.0/24 | Valid | None | 672 100% |
| 200.6.65.0/24 | Valid | None | 672 100% |
| 200.6.78.0/24 | Valid | None | 672 100% |
| 198.41.32.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 198.41.33.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 198.41.34.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 198.41.36.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 198.41.37.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 198.41.38.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 198.41.39.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 200.6.66.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 200.6.67.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 198.41.35.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 200.6.73.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
AS-SET
AS16874'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 30 are in fix.csv.
- ROA: none4
- Route object: none6
- Route object: RIR14
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.1.128.0/24 | No ROA covers it. Add a ROA for AS16874, maxLength 24. |
| Route object: none | 200.1.128.0/24 | Route objects for it name AS8151, AS28513. Add a route object with origin AS16874 in the RIR database for the space. |
| ROA: none | 192.231.110.0/24 | No ROA covers it. Add a ROA for AS16874, maxLength 24. |
| Route object: RIR | 192.231.110.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 200.0.156.0/24 | No ROA covers it. Add a ROA for AS16874, maxLength 24. |
| Route object: RIR | 200.0.156.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 200.2.75.0/24 | No ROA covers it. Add a ROA for AS16874, maxLength 24. |
| Route object: RIR | 200.2.75.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 198.41.41.0/24 | No route object for it. A route object for 198.41.40.0/22 with origin AS16874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16874 in the RIR database for the space. |
| Route object: none | 198.41.40.0/24 | No route object for it. A route object for 198.41.40.0/22 with origin AS16874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16874 in the RIR database for the space. |
| Route object: none | 200.0.158.0/24 | No route object for it. Add a route object with origin AS16874 in the RIR database for the space. |
| Route object: none | 200.6.65.0/24 | No route object for it. Add a route object with origin AS16874 in the RIR database for the space. |
| Route object: none | 200.6.78.0/24 | No route object for it. Add a route object with origin AS16874 in the RIR database for the space. |
| Route object: RIR | 198.41.32.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.41.33.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.41.34.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.41.36.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.41.37.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.41.38.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.41.39.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.6.66.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.6.67.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 198.41.35.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.6.73.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16874 whose prefix no peer sees AS16874 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 198.22.250.0/24 | RADB | No ROA |
| 198.41.40.0/21 | NTTCOM | No ROA |
| 198.41.40.0/22 | NTTCOM | No ROA |
| 200.6.71.0/24 | RADB | No ROA |
| 200.6.74.0/24 | NTTCOM | No ROA |
| 200.6.77.0/24 | NTTCOM | No ROA |
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.