Network · data from 2026-11-12
AS46191 5LINX-ASN - Globalinx
Registry name: 5LINX-ASN - Globalinx, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46191, 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.
| 199.73.86.0/23 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 199.73.86.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 199.73.87.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 199.96.214.0/23 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 199.96.215.0/24 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS46191 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 15 are in fix.csv.
- ROA: none5
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 199.73.86.0/23 | No ROA covers it. Add a ROA for AS46191, maxLength 23. |
| ROA: none | 199.73.86.0/24 | No ROA covers it. Add a ROA for AS46191, maxLength 24. |
| ROA: none | 199.73.87.0/24 | No ROA covers it. Add a ROA for AS46191, maxLength 24. |
| ROA: none | 199.96.214.0/23 | No ROA covers it. Add a ROA for AS46191, maxLength 23. |
| ROA: none | 199.96.215.0/24 | No ROA covers it. Add a ROA for AS46191, maxLength 24. |
Route objects not announced
Route objects with origin AS46191 whose prefix no peer sees AS46191 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 4.79.213.0/27 | ARIN | No ROA |
| 199.73.84.0/22 | ARIN | No ROA |
| 199.73.84.0/23 | ARIN | No ROA |
| 199.73.84.0/24 | ARIN | No ROA |
| 199.73.85.0/24 | ARIN | No ROA |
| 199.96.212.0/22 | ARIN, RADB | No ROA |
| 199.96.212.0/23 | ARIN | No ROA |
| 199.96.212.0/24 | ARIN | No ROA |
| 199.96.213.0/24 | ARIN | No ROA |
| 199.96.214.0/24 | 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.