Network · data from 2026-11-12
AS36563 TELX-DALLAS - Telx
Registry name: TELX-DALLAS - Telx, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36563, 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.
| 192.235.110.0/24 | No ROA | Nonecovered by 192.235.110.0/23 | 671 100% |
| 192.235.111.0/24 | No ROA | Nonecovered by 192.235.110.0/23 | 671 100% |
| 45.40.32.0/20 | No ROA | RIR databaseARIN | 673 100% |
| 45.56.204.0/22 | No ROA | RIR databaseARIN | 671 100% |
| 2606:cf80::/32 | No ROA | RIR databaseARIN | 635 100% |
AS-SET
AS36563 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 26 are in fix.csv.
- ROA: none5
- Route object: none2
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.235.110.0/24 | No ROA covers it. Add a ROA for AS36563, maxLength 24. |
| Route object: none | 192.235.110.0/24 | No route object for it. A route object for 192.235.110.0/23 with origin AS36563 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36563 in the RIR database for the space. |
| ROA: none | 192.235.111.0/24 | No ROA covers it. Add a ROA for AS36563, maxLength 24. |
| Route object: none | 192.235.111.0/24 | No route object for it. A route object for 192.235.110.0/23 with origin AS36563 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36563 in the RIR database for the space. |
| ROA: none | 45.40.32.0/20 | No ROA covers it. Add a ROA for AS36563, maxLength 20. |
| ROA: none | 45.56.204.0/22 | No ROA covers it. Add a ROA for AS36563, maxLength 22. |
| ROA: none | 2606:cf80::/32 | No ROA covers it. Add a ROA for AS36563, maxLength 32. |
Route objects not announced
Route objects with origin AS36563 whose prefix no peer sees AS36563 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 8.3.17.0/24 | RADB | No ROA |
| 67.23.48.0/24 | ALTDB | No ROA |
| 67.23.49.0/24 | ALTDB | No ROA |
| 67.23.52.0/24 | ALTDB | No ROA |
| 67.23.53.0/24 | ALTDB | No ROA |
| 67.23.60.0/24 | ALTDB | No ROA |
| 67.23.62.0/24 | ALTDB | No ROA |
| 67.23.63.0/24 | ALTDB | No ROA |
| 70.36.16.0/21 | ALTDB | No ROA |
| 70.36.25.0/24 | ALTDB | No ROA |
| 72.28.96.0/19 | ALTDB | No ROA |
| 72.28.100.0/24 | ALTDB | No ROA |
| 72.28.112.0/24 | ALTDB | No ROA |
| 72.28.122.0/24 | ALTDB | No ROA |
| 192.235.80.0/24 | ALTDB | No ROA |
| 192.235.110.0/23 | ALTDB | No ROA |
| 205.210.125.0/24 | ALTDB | No ROA |
| 208.65.109.0/24 | ALTDB | No ROA |
| 2607:fb58:f000::/36 | ALTDB | 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.