Network · data from 2026-11-12
AS16939 CARETECH-SOLUTIONS - CARETECH SOLUTIONS INC
Registry name: CARETECH-SOLUTIONS - CARETECH SOLUTIONS INC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16939, 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.
| 199.101.148.0/24 | No ROA | Nonecovered by 199.101.148.0/22 | 670 100% |
| 199.101.150.0/24 | No ROA | Nonecovered by 199.101.148.0/22 | 670 100% |
| 199.101.151.0/24 | No ROA | Nonecovered by 199.101.148.0/22 | 670 100% |
| 204.16.248.0/24 | No ROA | Nonecovered by 204.16.248.0/22 | 670 100% |
| 204.16.249.0/24 | No ROA | Nonecovered by 204.16.248.0/22 | 670 100% |
| 204.16.250.0/24 | No ROA | Nonecovered by 204.16.248.0/22 | 670 100% |
| 204.16.251.0/24 | No ROA | Nonecovered by 204.16.248.0/22 | 670 100% |
| 199.101.149.0/24 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS16939 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 17 are in fix.csv.
- ROA: none7
- Route object: none7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.101.148.0/24 | No ROA covers it. Add a ROA for AS16939, maxLength 24. |
| Route object: none | 199.101.148.0/24 | No route object for it. A route object for 199.101.148.0/22 with origin AS16939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16939 in the RIR database for the space. |
| ROA: none | 199.101.150.0/24 | No ROA covers it. Add a ROA for AS16939, maxLength 24. |
| Route object: none | 199.101.150.0/24 | No route object for it. A route object for 199.101.148.0/22 with origin AS16939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16939 in the RIR database for the space. |
| ROA: none | 199.101.151.0/24 | No ROA covers it. Add a ROA for AS16939, maxLength 24. |
| Route object: none | 199.101.151.0/24 | No route object for it. A route object for 199.101.148.0/22 with origin AS16939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16939 in the RIR database for the space. |
| ROA: none | 204.16.248.0/24 | No ROA covers it. Add a ROA for AS16939, maxLength 24. |
| Route object: none | 204.16.248.0/24 | No route object for it. A route object for 204.16.248.0/22 with origin AS16939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16939 in the RIR database for the space. |
| ROA: none | 204.16.249.0/24 | No ROA covers it. Add a ROA for AS16939, maxLength 24. |
| Route object: none | 204.16.249.0/24 | No route object for it. A route object for 204.16.248.0/22 with origin AS16939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16939 in the RIR database for the space. |
| ROA: none | 204.16.250.0/24 | No ROA covers it. Add a ROA for AS16939, maxLength 24. |
| Route object: none | 204.16.250.0/24 | No route object for it. A route object for 204.16.248.0/22 with origin AS16939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16939 in the RIR database for the space. |
| ROA: none | 204.16.251.0/24 | No ROA covers it. Add a ROA for AS16939, maxLength 24. |
| Route object: none | 204.16.251.0/24 | No route object for it. A route object for 204.16.248.0/22 with origin AS16939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16939 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16939 whose prefix no peer sees AS16939 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.159.63.0/24 | RADB | No ROA |
| 199.101.148.0/22 | RADB | No ROA |
| 204.16.248.0/22 | ARIN, 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.