Network · data from 2026-11-12
AS16887 AETHERNETSANANTONIO - Aethernet LLC
Registry name: AETHERNETSANANTONIO - Aethernet LLC, US · not in PeeringDB
12IPv4 routes
0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
12No ROA
12 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS16887, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS16887, 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.
| 173.226.142.0/24 | No ROA | None | 671 100% |
| 173.226.143.0/24 | No ROA | None | 671 100% |
| 192.171.116.0/24 | No ROA | Nonecovered by 192.171.116.0/22 | 671 100% |
| 192.171.117.0/24 | No ROA | Nonecovered by 192.171.116.0/22 | 671 100% |
| 192.171.118.0/24 | No ROA | Nonecovered by 192.171.116.0/22 | 671 100% |
| 192.171.119.0/24 | No ROA | Nonecovered by 192.171.116.0/22 | 671 100% |
| 199.193.216.0/24 | No ROA | Nonecovered by 199.193.216.0/21 | 671 100% |
| 199.193.217.0/24 | No ROA | Nonecovered by 199.193.216.0/21 | 671 100% |
| 199.193.220.0/24 | No ROA | Nonecovered by 199.193.216.0/21 | 671 100% |
| 199.193.221.0/24 | No ROA | Nonecovered by 199.193.216.0/21 | 671 100% |
| 199.193.222.0/24 | No ROA | Nonecovered by 199.193.216.0/21 | 671 100% |
| 199.193.223.0/24 | No ROA | Nonecovered by 199.193.216.0/21 | 671 100% |
AS-SET
AS16887 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 26 are in fix.csv.
- ROA: none12
- Route object: none12
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 173.226.142.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 173.226.142.0/24 | No route object for it. Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 173.226.143.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 173.226.143.0/24 | No route object for it. Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 192.171.116.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 192.171.116.0/24 | No route object for it. A route object for 192.171.116.0/22 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 192.171.117.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 192.171.117.0/24 | No route object for it. A route object for 192.171.116.0/22 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 192.171.118.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 192.171.118.0/24 | No route object for it. A route object for 192.171.116.0/22 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 192.171.119.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 192.171.119.0/24 | No route object for it. A route object for 192.171.116.0/22 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 199.193.216.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 199.193.216.0/24 | No route object for it. A route object for 199.193.216.0/21 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 199.193.217.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 199.193.217.0/24 | No route object for it. A route object for 199.193.216.0/21 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 199.193.220.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 199.193.220.0/24 | No route object for it. A route object for 199.193.216.0/21 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 199.193.221.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 199.193.221.0/24 | No route object for it. A route object for 199.193.216.0/21 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 199.193.222.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 199.193.222.0/24 | No route object for it. A route object for 199.193.216.0/21 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
| ROA: none | 199.193.223.0/24 | No ROA covers it. Add a ROA for AS16887, maxLength 24. |
| Route object: none | 199.193.223.0/24 | No route object for it. A route object for 199.193.216.0/21 with origin AS16887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16887 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16887 whose prefix no peer sees AS16887 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.171.116.0/22 | RADB | No ROA |
| 199.193.216.0/21 | RADB | 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.