Network · data from 2026-11-12
AS63201 COEOSOLUTIONS - Coeo Solutions, LLC
Registry name: COEOSOLUTIONS - Coeo Solutions, LLC, US · not in PeeringDB
20IPv4 routes
95.0% RPKI valid · 55.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
1No ROA
9 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS63201, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS63201, 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.
| 192.234.93.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 52.129.36.0/24 | Valid | Nonecovered by 52.129.36.0/23 | 673 100% |
| 104.193.118.0/24 | Valid | Nonecovered by 104.193.118.0/23 | 673 100% |
| 104.193.119.0/24 | Valid | Nonecovered by 104.193.118.0/23 | 673 100% |
| 161.38.186.0/24 | Valid | Nonecovered by 161.38.186.0/23 | 673 100% |
| 161.38.187.0/24 | Valid | Nonecovered by 161.38.186.0/23 | 673 100% |
| 204.68.232.0/24 | Valid | Nonecovered by 204.68.232.0/23 | 673 100% |
| 204.68.233.0/24 | Valid | Nonecovered by 204.68.232.0/23 | 673 100% |
| 213.159.132.0/23 | Valid | Nonecovered by 213.159.132.0/22 | 673 100% |
| 213.159.134.0/23 | Valid | Nonecovered by 213.159.132.0/22 | 673 100% |
| 104.193.118.0/23 | Valid | RIR databaseARIN | 673 100% |
| 141.193.235.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 147.160.168.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 148.59.214.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 161.199.19.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 161.199.246.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 204.68.232.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 204.225.124.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 205.174.158.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 147.185.190.0/24 | Valid | RIR databaseARIN, RADB | 1 0%low visibility |
AS-SET
AS63201 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 16 are in fix.csv.
- ROA: none1
- Route object: none9
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.234.93.0/24 | No ROA covers it. Add a ROA for AS63201, maxLength 24. |
| Route object: RIR | 192.234.93.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 52.129.36.0/24 | No route object for it. A route object for 52.129.36.0/23 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
| Route object: none | 104.193.118.0/24 | No route object for it. A route object for 104.193.118.0/23 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
| Route object: none | 104.193.119.0/24 | No route object for it. A route object for 104.193.118.0/23 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
| Route object: none | 161.38.186.0/24 | No route object for it. A route object for 161.38.186.0/23 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
| Route object: none | 161.38.187.0/24 | No route object for it. A route object for 161.38.186.0/23 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
| Route object: none | 204.68.232.0/24 | No route object for it. A route object for 204.68.232.0/23 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
| Route object: none | 204.68.233.0/24 | No route object for it. A route object for 204.68.232.0/23 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
| Route object: none | 213.159.132.0/23 | No route object for it. A route object for 213.159.132.0/22 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
| Route object: none | 213.159.134.0/23 | No route object for it. A route object for 213.159.132.0/22 with origin AS63201 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63201 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS63201 whose prefix no peer sees AS63201 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 52.129.36.0/23 | ARIN, RADB | Valid |
| 104.193.116.0/22 | RADB | No ROA |
| 161.38.186.0/23 | ARIN, RADB | Valid |
| 206.223.98.0/24 | ARIN | No ROA |
| 213.159.132.0/22 | ARIN, RADB | 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.