Network · data from 2026-11-12
AS394232 TELKEL
Registry name: TELKEL-MTL - TelKel inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394232, 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.
| 23.252.228.0/24 | Invalid: maxLength | Nonecovered by 23.252.224.0/20 | 45 7%low visibility |
| 69.57.223.0/24 | No ROA | Other IRR onlyALTDB | 669 99% |
| 130.12.87.0/24 | No ROA | Other IRR onlyALTDB | 669 99% |
| 23.134.32.0/24 | Valid | RIR databaseARIN | 669 99% |
| 2604:d040::/32 | Valid | RIR databaseARIN | 635 100% |
| 2606:7480::/32 | Valid | RIR databaseALTDB, ARIN | 635 100% |
| 23.178.0.0/24 | Valid | RIR databaseALTDB, ARIN | 253 38% |
| 23.178.1.0/24 | Valid | RIR databaseALTDB, ARIN | 253 38% |
| 23.252.224.0/20 | Valid | RIR databaseALTDB, ARIN | 253 38% |
| 199.4.190.0/24 | Valid | RIR databaseALTDB, ARIN | 253 38% |
AS-SET
PeeringDB's irr_as_set for AS394232: AS394232:AS-TELKEL. 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 (AS394232 isn't in the set, or no route object for AS394232 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 | AS394232 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS394232:AS-TELKEL | In no IRR database read today. | |||||
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 9 are in fix.csv.
- ROA: maxLength1
- ROA: none2
- Route object: none1
- Route object: RIR2
- AS-SET: not found1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 23.252.228.0/24 | ROA 23.252.224.0/20 AS394232 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 23.252.228.0/24. |
| Route object: none | 23.252.228.0/24 | No route object for it. A route object for 23.252.224.0/20 with origin AS394232 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394232 in the RIR database for the space. |
| ROA: none | 69.57.223.0/24 | No ROA covers it. Add a ROA for AS394232, maxLength 24. |
| Route object: RIR | 69.57.223.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 130.12.87.0/24 | No ROA covers it. Add a ROA for AS394232, maxLength 24. |
| Route object: RIR | 130.12.87.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| AS-SET: not found | AS394232:AS-TELKEL | PeeringDB names AS394232:AS-TELKEL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS394232 whose prefix no peer sees AS394232 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.114.16.0/21 | ARIN | Valid |
| 165.140.172.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.