Network · data from 2026-11-12
AS23261 NCS Managed Services Inc
Registry name: NCS-MSI - NCS Managed Services Inc, CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23261, 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.
| 149.18.192.0/20 | No ROA | Other IRR onlyRADB | 672 100% |
| 136.175.116.0/24 | Valid | Nonecovered by 136.175.116.0/22 | 670 100% |
| 136.175.117.0/24 | Valid | Nonecovered by 136.175.116.0/22 | 670 100% |
| 136.175.118.0/24 | Valid | Nonecovered by 136.175.116.0/22 | 670 100% |
| 136.175.119.0/24 | Valid | Nonecovered by 136.175.116.0/22 | 670 100% |
| 23.131.112.0/24 | Valid | RIR databaseARIN | 670 100% |
| 66.235.100.0/22 | Valid | RIR databaseARIN | 670 100% |
| 156.9.4.0/22 | Valid | RIR databaseARIN | 669 99% |
| 2605:2e40::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS23261: AS-NCS-MSI. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS23261 isn't in the set, or no route object for AS23261 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS23261 in it | Not covered |
|---|---|---|---|---|---|
| AS-NCS-MSI | ARIN | 1 | 1 | Yes | 0 |
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 8 are in fix.csv.
- ROA: none1
- Route object: none4
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.18.192.0/20 | No ROA covers it. Add a ROA for AS23261, maxLength 20. |
| Route object: RIR | 149.18.192.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 136.175.116.0/24 | No route object for it. A route object for 136.175.116.0/22 with origin AS23261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23261 in the RIR database for the space. |
| Route object: none | 136.175.117.0/24 | No route object for it. A route object for 136.175.116.0/22 with origin AS23261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23261 in the RIR database for the space. |
| Route object: none | 136.175.118.0/24 | No route object for it. A route object for 136.175.116.0/22 with origin AS23261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23261 in the RIR database for the space. |
| Route object: none | 136.175.119.0/24 | No route object for it. A route object for 136.175.116.0/22 with origin AS23261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23261 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23261 whose prefix no peer sees AS23261 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.168.217.0/24 | ALTDB | No ROA |
| 136.175.116.0/22 | ARIN | 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.