Network · data from 2026-11-12
AS209801 VF Virtual Future sp. z o.o.
Registry name: VF Virtual Future sp. z o.o., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209801, 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.
| 81.6.133.0/24 | Invalid: origin | RIR databaseRIPE | 61 9%low visibility |
| 91.234.246.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2001:678:8a4::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 192.88.204.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.92.84.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS209801 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
- ROA: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 81.6.133.0/24 | ROAs covering it name AS30778, not AS209801. If AS209801 should announce it, add a ROA for AS209801. |
| ROA: none | 91.234.246.0/24 | No ROA covers it. Add a ROA for AS209801, maxLength 24. |
| ROA: none | 2001:678:8a4::/48 | No ROA covers it. Add a ROA for AS209801, maxLength 48. |
Route objects not announced
Route objects with origin AS209801 whose prefix no peer sees AS209801 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:16ae::/64 | 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.