Network · data from 2026-11-12
AS49776 GORSET-AS Gorset LLC
Registry name: GORSET-AS Gorset LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49776, 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.
| 185.126.192.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.180.248.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 213.108.216.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 31.40.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 176.122.64.0/20 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS49776 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 5 are in fix.csv.
- ROA: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.126.192.0/22 | No ROA covers it. Add a ROA for AS49776, maxLength 22. |
| ROA: none | 185.180.248.0/22 | No ROA covers it. Add a ROA for AS49776, maxLength 22. |
| ROA: none | 213.108.216.0/21 | No ROA covers it. Add a ROA for AS49776, maxLength 21. |
Route objects not announced
Route objects with origin AS49776 whose prefix no peer sees AS49776 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 213.108.216.0/22 | RIPE | No ROA |
| 213.108.216.64/27 | 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.