Network · data from 2026-11-12
AS49800 GNC-Alfa CJSC
Registry name: GNC-ALFA GNC-Alfa CJSC, AM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49800, 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.
| 206.62.192.0/19 | Invalid: origin | None | 21 3%low visibility |
| 45.146.36.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.8.2.0/24 | Valid | Nonecovered by 185.8.0.0/22 | 673 100% |
| 5.63.160.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 31.47.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 37.186.64.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 46.19.96.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 62.89.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 78.109.64.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 93.185.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 130.193.120.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.8.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.250.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 37.186.84.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 37.186.93.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a03:6947:200::/40 | Valid | RIR databaseRIPE | 636 100% |
| 2a02:2a50::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS49800: AS-GNC. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS49800 isn't in the set, or no route object for AS49800 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS49800 in it | Not covered |
|---|---|---|---|---|---|
| AS-GNC | RIPElists itself further down | 154 | 9 | Yes | 1 |
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: origin1
- ROA: none1
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 206.62.192.0/19 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS49800 should announce it, add a ROA for AS49800. |
| Route object: none | 206.62.192.0/19 | No route object for it. Add a route object with origin AS49800 in the RIR database for the space. |
| ROA: none | 45.146.36.0/22 | No ROA covers it. Add a ROA for AS49800, maxLength 22. |
| Route object: none | 185.8.2.0/24 | No route object for it. A route object for 185.8.0.0/22 with origin AS49800 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49800 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49800 whose prefix no peer sees AS49800 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.186.80.0/22 | RIPE | 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.