Network · data from 2026-11-12
AS1347 VOYANT-LAB - Inteliquent, inc.
Registry name: VOYANT-LAB - Inteliquent, inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS1347, 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.
| 204.72.175.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 137.192.21.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 198.174.57.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 204.73.218.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 206.145.172.0/22 | No ROA | RIR databaseARIN | 672 100% |
AS-SET
AS1347 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 13 are in fix.csv.
- ROA: none5
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.72.175.0/24 | No ROA covers it. Add a ROA for AS1347, maxLength 24. |
| ROA: none | 137.192.21.0/24 | No ROA covers it. Add a ROA for AS1347, maxLength 24. |
| ROA: none | 198.174.57.0/24 | No ROA covers it. Add a ROA for AS1347, maxLength 24. |
| ROA: none | 204.73.218.0/24 | No ROA covers it. Add a ROA for AS1347, maxLength 24. |
| ROA: none | 206.145.172.0/22 | No ROA covers it. Add a ROA for AS1347, maxLength 22. |
Route objects not announced
Route objects with origin AS1347 whose prefix no peer sees AS1347 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 137.192.0.0/16 | ARIN | No ROA |
| 137.192.196.0/24 | ARIN | No ROA |
| 198.174.0.0/16 | ARIN | No ROA |
| 204.72.0.0/15 | ARIN | No ROA |
| 206.144.0.0/14 | ARIN | No ROA |
| 2604:3000::/32 | ARIN | Valid |
| 2604:d380::/32 | ARIN | Valid |
| 2605:6d80::/32 | 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.