Network · data from 2026-11-12
AS49830 Goldlink
Registry name: GOLDLINK-AS RESET LLC, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49830, 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.
| 46.149.101.0/24 | No ROA | RIR databaseRIPE | 668 99% |
| 185.42.180.0/22 | No ROA | RIR databaseRIPE | 668 99% |
| 109.68.72.0/21 | No ROA | RIR databaseRIPE | 667 99% |
AS-SET
AS49830's PeeringDB record names no 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 4 are in fix.csv.
- ROA: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.149.101.0/24 | No ROA covers it. Add a ROA for AS49830, maxLength 24. |
| ROA: none | 185.42.180.0/22 | No ROA covers it. Add a ROA for AS49830, maxLength 22. |
| ROA: none | 109.68.72.0/21 | No ROA covers it. Add a ROA for AS49830, maxLength 21. |
Route objects not announced
Route objects with origin AS49830 whose prefix no peer sees AS49830 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.68.72.0/25 | RIPE | 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.