Network · data from 2026-11-12
AS11192 SMART-CITY-HQ - SMART CITY NETWORKS, LIMITED PARTNERSHIP
Registry name: SMART-CITY-HQ - SMART CITY NETWORKS, LIMITED PARTNERSHIP, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11192, 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.
| 66.78.202.0/24 | Valid | Nonecovered by 66.78.200.0/21 | 672 100% |
| 66.78.203.0/24 | Valid | Nonecovered by 66.78.200.0/21 | 672 100% |
| 66.78.207.0/24 | Valid | Nonecovered by 66.78.200.0/21 | 672 100% |
| 66.78.244.0/24 | Valid | Nonecovered by 66.78.244.0/23 | 672 100% |
| 66.78.245.0/24 | Valid | Nonecovered by 66.78.244.0/23 | 672 100% |
| 24.56.133.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 24.56.136.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 24.56.140.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 24.56.184.0/22 | Valid | RIR databaseARIN, RADB | 672 100% |
| 24.75.228.0/22 | Valid | RIR databaseARIN, RADB | 672 100% |
| 24.75.240.0/22 | Valid | RIR databaseARIN, RADB | 672 100% |
| 24.236.56.0/22 | Valid | RIR databaseARIN, RADB | 672 100% |
| 66.78.200.0/21 | Valid | RIR databaseARIN | 672 100% |
| 66.78.232.0/22 | Valid | RIR databaseARIN | 672 100% |
| 66.78.242.0/23 | Valid | RIR databaseARIN | 672 100% |
| 66.78.250.0/23 | Valid | RIR databaseARIN | 672 100% |
| 66.78.252.0/24 | Valid | RIR databaseARIN | 672 100% |
| 66.78.253.0/24 | Valid | RIR databaseARIN | 672 100% |
| 67.217.0.0/22 | Valid | RIR databaseARIN, RADB | 672 100% |
| 96.8.34.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 96.8.36.0/22 | Valid | RIR databaseARIN, RADB | 672 100% |
| 96.8.40.0/22 | Valid | RIR databaseARIN, RADB | 672 100% |
| 208.115.76.0/23 | Valid | RIR databaseARIN, RADB | 672 100% |
| 208.115.81.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 208.115.82.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 208.115.92.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
AS-SET
AS11192 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 33 are in fix.csv.
- Route object: none5
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 66.78.202.0/24 | No route object for it. A route object for 66.78.200.0/21 with origin AS11192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11192 in the RIR database for the space. |
| Route object: none | 66.78.203.0/24 | No route object for it. A route object for 66.78.200.0/21 with origin AS11192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11192 in the RIR database for the space. |
| Route object: none | 66.78.207.0/24 | No route object for it. A route object for 66.78.200.0/21 with origin AS11192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11192 in the RIR database for the space. |
| Route object: none | 66.78.244.0/24 | No route object for it. A route object for 66.78.244.0/23 with origin AS11192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11192 in the RIR database for the space. |
| Route object: none | 66.78.245.0/24 | No route object for it. A route object for 66.78.244.0/23 with origin AS11192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11192 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11192 whose prefix no peer sees AS11192 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.92.192.0/22 | RADB | No ROA |
| 23.92.204.0/22 | RADB | No ROA |
| 24.56.132.0/24 | RADB | No ROA |
| 24.75.208.0/21 | RADB | No ROA |
| 24.75.232.0/21 | RADB | No ROA |
| 66.78.192.0/18 | RADB | No ROA |
| 66.78.244.0/23 | ARIN | Valid |
| 66.78.246.0/23 | RADB | No ROA |
| 96.8.46.0/23 | RADB | No ROA |
| 96.8.48.0/20 | BBOI, RADB | No ROA |
| 128.64.0.0/16 | RADB | No ROA |
| 128.64.128.0/22 | BBOI | No ROA |
| 128.64.132.0/23 | BBOI | No ROA |
| 128.64.134.0/24 | BBOI | No ROA |
| 128.64.142.0/24 | BBOI | No ROA |
| 128.64.146.0/23 | BBOI | No ROA |
| 130.129.0.0/16 | RADB | No ROA |
| 199.45.0.0/21 | RADB | No ROA |
| 207.189.32.0/19 | RADB | No ROA |
| 208.115.67.0/24 | RADB | No ROA |
| 208.115.88.0/24 | RADB | No ROA |
| 208.115.90.0/23 | RADB | No ROA |
| 208.115.93.0/24 | BBOI, RADB | No ROA |
| 216.222.93.0/24 | BBOI | Invalid: origin |
| 216.222.94.0/24 | BBOI | Invalid: origin |
| 216.222.95.0/24 | BBOI | Invalid: origin |
| 2604:b180::/32 | RADB | No ROA |
| 2604:b180:170::/44 | 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.