Network · data from 2026-11-12
AS214879 SKYVPN STANISLAV SAVOV
Registry name: SKYVPN STANISLAV SAVOV, BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214879, 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.
| 92.113.118.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 102.216.83.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 31.57.128.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
AS-SET
AS214879 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 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 92.113.118.0/24 | ROAs covering it name AS402265, not AS214879. If AS214879 should announce it, add a ROA for AS214879. |
| Route object: none | 92.113.118.0/24 | Route objects for it name AS402265. Add a route object with origin AS214879 in the RIR database for the space. |
| Route object: RIR | 102.216.83.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS214879 whose prefix no peer sees AS214879 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0c:b641:c60::/44 | 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.