Network · data from 2026-11-12
AS35026 GELICON-AS Gelicon-Apple Limited liability company
Registry name: GELICON-AS Gelicon-Apple Limited liability company, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35026, 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.
| 2a03:cf40::/32 | No ROA | None | 458 72% |
| 2a03:cf40::/56 | No ROA | Nonecovered by 2a03:cf40::/40 | 6 1%low visibility |
| 2a03:cf40:0:1::/64 | No ROA | Nonecovered by 2a03:cf40::/40 | 5 1%low visibility |
| 2a03:cf40:0:1002::/64 | No ROA | Nonecovered by 2a03:cf40::/40 | 5 1%low visibility |
| 2a03:cf40:0:1005::/64 | No ROA | Nonecovered by 2a03:cf40::/40 | 5 1%low visibility |
| 37.139.84.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 37.139.86.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a03:cf40::/40 | No ROA | RIR databaseRIPE | 636 100% |
| 37.139.84.0/24 | No ROA | RIR databaseRIPE | 66 10%low visibility |
| 37.139.85.0/24 | No ROA | RIR databaseRIPE | 66 10%low visibility |
| 37.139.84.0/22 | No ROA | RIR databaseRIPE | 64 10%low visibility |
AS-SET
AS35026 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 17 are in fix.csv.
- ROA: none11
- Route object: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a03:cf40::/32 | No ROA covers it. Add a ROA for AS35026, maxLength 32. |
| Route object: none | 2a03:cf40::/32 | No route object for it. Add a route object with origin AS35026 in the RIR database for the space. |
| ROA: none | 2a03:cf40::/56 | No ROA covers it. Add a ROA for AS35026, maxLength 56. |
| Route object: none | 2a03:cf40::/56 | No route object for it. A route object for 2a03:cf40::/40 with origin AS35026 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS35026 in the RIR database for the space. |
| ROA: none | 2a03:cf40:0:1::/64 | No ROA covers it. Add a ROA for AS35026, maxLength 64. |
| Route object: none | 2a03:cf40:0:1::/64 | No route object for it. A route object for 2a03:cf40::/40 with origin AS35026 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS35026 in the RIR database for the space. |
| ROA: none | 2a03:cf40:0:1002::/64 | No ROA covers it. Add a ROA for AS35026, maxLength 64. |
| Route object: none | 2a03:cf40:0:1002::/64 | No route object for it. A route object for 2a03:cf40::/40 with origin AS35026 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS35026 in the RIR database for the space. |
| ROA: none | 2a03:cf40:0:1005::/64 | No ROA covers it. Add a ROA for AS35026, maxLength 64. |
| Route object: none | 2a03:cf40:0:1005::/64 | No route object for it. A route object for 2a03:cf40::/40 with origin AS35026 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS35026 in the RIR database for the space. |
| ROA: none | 37.139.84.0/23 | No ROA covers it. Add a ROA for AS35026, maxLength 23. |
| ROA: none | 37.139.86.0/24 | No ROA covers it. Add a ROA for AS35026, maxLength 24. |
| ROA: none | 2a03:cf40::/40 | No ROA covers it. Add a ROA for AS35026, maxLength 40. |
| ROA: none | 37.139.84.0/24 | No ROA covers it. Add a ROA for AS35026, maxLength 24. |
| ROA: none | 37.139.85.0/24 | No ROA covers it. Add a ROA for AS35026, maxLength 24. |
| ROA: none | 37.139.84.0/22 | No ROA covers it. Add a ROA for AS35026, maxLength 22. |
Route objects not announced
Route objects with origin AS35026 whose prefix no peer sees AS35026 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.139.86.0/23 | 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.