Network · data from 2026-11-12
AS19816 NCS DataCom
Registry name: NCSDATACOM - NCS DataCom, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19816, 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.
| 206.180.160.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.161.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.162.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.163.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.164.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.165.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.166.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.167.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.168.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.169.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.171.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.172.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.180.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.181.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.182.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.183.0/24 | No ROA | Nonecovered by 206.180.160.0/19 | 671 100% |
| 206.180.160.0/19 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS19816'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 38 are in fix.csv.
- ROA: none17
- Route object: none16
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 206.180.160.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.160.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.161.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.161.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.162.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.162.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.163.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.163.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.164.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.164.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.165.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.165.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.166.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.166.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.167.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.167.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.168.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.168.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.169.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.169.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.171.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.171.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.172.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.172.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.180.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.180.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.181.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.181.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.182.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.182.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.183.0/24 | No ROA covers it. Add a ROA for AS19816, maxLength 24. |
| Route object: none | 206.180.183.0/24 | No route object for it. A route object for 206.180.160.0/19 with origin AS19816 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19816 in the RIR database for the space. |
| ROA: none | 206.180.160.0/19 | No ROA covers it. Add a ROA for AS19816, maxLength 19. |
| Route object: RIR | 206.180.160.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19816 whose prefix no peer sees AS19816 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 173.211.108.0/22 | ARIN, RADB | Valid |
| 174.140.232.0/24 | ARIN, RADB | Valid |
| 174.140.235.0/24 | ARIN, RADB | Valid |
| 216.41.144.0/20 | 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.