Network · data from 2026-11-12
AS46719 COMCELL4236207 - COMCELL INC.
Registry name: COMCELL4236207 - COMCELL INC., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46719, 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.
| 140.106.208.0/20 | Valid | None | 673 100% |
| 140.106.210.0/24 | Valid | None | 673 100% |
| 140.106.216.0/24 | Valid | None | 673 100% |
| 140.106.217.0/24 | Valid | None | 673 100% |
| 140.106.223.0/24 | Valid | None | 673 100% |
| 199.167.132.0/24 | Valid | Nonecovered by 199.167.132.0/22 | 673 100% |
| 199.167.133.0/24 | Valid | Nonecovered by 199.167.132.0/22 | 673 100% |
| 199.167.134.0/24 | Valid | Nonecovered by 199.167.132.0/22 | 670 100% |
| 199.167.135.0/24 | Valid | Nonecovered by 199.167.132.0/22 | 670 100% |
| 199.188.240.0/22 | Valid | None | 670 100% |
| 199.188.240.0/23 | Valid | None | 670 100% |
| 199.188.242.0/23 | Valid | None | 670 100% |
| 204.154.240.0/21 | Valid | None | 670 100% |
| 204.154.240.0/22 | Valid | None | 670 100% |
| 204.154.244.0/22 | Valid | None | 670 100% |
| 206.190.228.0/22 | Valid | None | 670 100% |
| 206.190.228.0/23 | Valid | None | 670 100% |
| 206.190.230.0/23 | Valid | None | 670 100% |
| 216.213.112.0/20 | Valid | None | 670 100% |
| 216.213.120.0/23 | Valid | None | 670 100% |
| 216.213.122.0/23 | Valid | None | 670 100% |
| 216.213.124.0/23 | Valid | None | 670 100% |
| 216.213.126.0/24 | Valid | None | 670 100% |
| 216.213.127.0/24 | Valid | None | 670 100% |
| 199.167.132.0/22 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS46719 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 24 are in fix.csv.
- Route object: none24
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 140.106.208.0/20 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 140.106.210.0/24 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 140.106.216.0/24 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 140.106.217.0/24 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 140.106.223.0/24 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 199.167.132.0/24 | No route object for it. A route object for 199.167.132.0/22 with origin AS46719 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 199.167.133.0/24 | No route object for it. A route object for 199.167.132.0/22 with origin AS46719 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 199.167.134.0/24 | No route object for it. A route object for 199.167.132.0/22 with origin AS46719 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 199.167.135.0/24 | No route object for it. A route object for 199.167.132.0/22 with origin AS46719 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 199.188.240.0/22 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 199.188.240.0/23 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 199.188.242.0/23 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 204.154.240.0/21 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 204.154.240.0/22 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 204.154.244.0/22 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 206.190.228.0/22 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 206.190.228.0/23 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 206.190.230.0/23 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 216.213.112.0/20 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 216.213.120.0/23 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 216.213.122.0/23 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 216.213.124.0/23 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 216.213.126.0/24 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
| Route object: none | 216.213.127.0/24 | No route object for it. Add a route object with origin AS46719 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS46719 is announced.
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.