Network · data from 2026-11-12
AS46872 GLDATACENTRE-1 - Gold Line Telemanagement, Inc.
Registry name: GLDATACENTRE-1 - Gold Line Telemanagement, Inc., CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46872, 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.17.169.0/24 | Invalid: origin | None | 125 19% |
| 207.107.146.0/24 | Invalid: origin | None | 125 19% |
| 192.251.198.0/24 | No ROA | Nonecovered by 192.251.198.0/23 | 671 100% |
| 192.251.199.0/24 | No ROA | Nonecovered by 192.251.198.0/23 | 671 100% |
| 162.248.168.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 162.248.169.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 162.248.170.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 162.248.171.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 204.101.238.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 184.104.186.0/24 | Valid | RIR databaseARIN | 670 100% |
AS-SET
AS46872 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 20 are in fix.csv.
- ROA: origin2
- ROA: none6
- Route object: none4
- Route object: RIR5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 69.17.169.0/24 | ROAs covering it name AS812, not AS46872. If AS46872 should announce it, add a ROA for AS46872. |
| Route object: none | 69.17.169.0/24 | No route object for it. Add a route object with origin AS46872 in the RIR database for the space. |
| ROA: origin | 207.107.146.0/24 | ROAs covering it name AS812, not AS46872. If AS46872 should announce it, add a ROA for AS46872. |
| Route object: none | 207.107.146.0/24 | No route object for it. Add a route object with origin AS46872 in the RIR database for the space. |
| ROA: none | 192.251.198.0/24 | No ROA covers it. Add a ROA for AS46872, maxLength 24. |
| Route object: none | 192.251.198.0/24 | No route object for it. A route object for 192.251.198.0/23 with origin AS46872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46872 in the RIR database for the space. |
| ROA: none | 192.251.199.0/24 | No ROA covers it. Add a ROA for AS46872, maxLength 24. |
| Route object: none | 192.251.199.0/24 | No route object for it. A route object for 192.251.198.0/23 with origin AS46872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46872 in the RIR database for the space. |
| ROA: none | 162.248.168.0/24 | No ROA covers it. Add a ROA for AS46872, maxLength 24. |
| Route object: RIR | 162.248.168.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 162.248.169.0/24 | No ROA covers it. Add a ROA for AS46872, maxLength 24. |
| Route object: RIR | 162.248.169.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 162.248.170.0/24 | No ROA covers it. Add a ROA for AS46872, maxLength 24. |
| Route object: RIR | 162.248.170.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 162.248.171.0/24 | No ROA covers it. Add a ROA for AS46872, maxLength 24. |
| Route object: RIR | 162.248.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 204.101.238.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46872 whose prefix no peer sees AS46872 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.118.134.0/24 | ARIN | No ROA |
| 192.251.198.0/23 | RADB | No ROA |
| 216.66.42.0/24 | 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.