Network · data from 2026-11-12
AS26859 TELENET-INTL - Fortis Communications, Inc.
Registry name: TELENET-INTL - Fortis Communications, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26859, 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.
| 69.67.96.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS26859 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 12 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.67.96.0/20 | No ROA covers it. Add a ROA for AS26859, maxLength 20. |
| Route object: RIR | 69.67.96.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS26859 whose prefix no peer sees AS26859 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.116.128.0/22 | RADB | No ROA |
| 66.28.19.0/24 | RADB | No ROA |
| 66.28.52.0/22 | RADB | No ROA |
| 66.28.80.0/24 | RADB | No ROA |
| 66.28.160.0/22 | RADB | No ROA |
| 66.250.152.0/24 | RADB | No ROA |
| 66.250.184.0/22 | RADB | No ROA |
| 69.67.98.0/24 | RADB | No ROA |
| 69.67.107.0/24 | RADB | No ROA |
| 69.67.110.0/24 | 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.