Network · data from 2026-11-12
AS32473 EHTEL
Registry name: EHTEL - Eh!Tel Networks Inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS32473, 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.
| 38.29.148.0/23 | No ROA | Nonecovered by 38.29.148.0/22 | 673 100% |
| 38.2.156.0/23 | No ROA | Nonecovered by 38.2.156.0/22 | 672 100% |
| 38.2.158.0/24 | No ROA | Nonecovered by 38.2.156.0/22 | 671 100% |
| 38.2.159.0/24 | No ROA | Nonecovered by 38.2.156.0/22 | 671 100% |
| 67.158.61.0/24 | Valid | RIR databaseARIN | 673 100% |
| 141.193.149.0/24 | Valid | RIR databaseARIN | 673 100% |
| 69.72.30.0/24 | Valid | RIR databaseARIN | 672 100% |
| 137.83.90.0/24 | Valid | RIR databaseARIN | 672 100% |
| 172.86.159.0/24 | Valid | RIR databaseARIN | 672 100% |
| 64.52.21.0/24 | Valid | RIR databaseARIN | 670 100% |
| 2605:6740::/32 | Valid | RIR databaseARIN | 605 95% |
AS-SET
PeeringDB's irr_as_set for AS32473: ARIN::AS-EHTEL. 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 (AS32473 isn't in the set, or no route object for AS32473 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 | AS32473 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-EHTEL | 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 11 are in fix.csv.
- ROA: none4
- Route object: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.29.148.0/23 | No ROA covers it. Add a ROA for AS32473, maxLength 23. |
| Route object: none | 38.29.148.0/23 | No route object for it. A route object for 38.29.148.0/22 with origin AS32473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32473 in the RIR database for the space. |
| ROA: none | 38.2.156.0/23 | No ROA covers it. Add a ROA for AS32473, maxLength 23. |
| Route object: none | 38.2.156.0/23 | No route object for it. A route object for 38.2.156.0/22 with origin AS32473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32473 in the RIR database for the space. |
| ROA: none | 38.2.158.0/24 | No ROA covers it. Add a ROA for AS32473, maxLength 24. |
| Route object: none | 38.2.158.0/24 | No route object for it. A route object for 38.2.156.0/22 with origin AS32473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32473 in the RIR database for the space. |
| ROA: none | 38.2.159.0/24 | No ROA covers it. Add a ROA for AS32473, maxLength 24. |
| Route object: none | 38.2.159.0/24 | No route object for it. A route object for 38.2.156.0/22 with origin AS32473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32473 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS32473 whose prefix no peer sees AS32473 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 8.9.192.0/19 | RADB | No ROA |
| 38.2.156.0/22 | RADB | No ROA |
| 38.29.148.0/22 | ARIN | 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.