Network · data from 2026-11-12
AS209866 Vort Cloud
Registry name: VORT Piotr Macha trading as Vort Cloud, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209866, 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.
| 201.3.121.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 201.3.120.0/23 | No ROA | None | 2 0%low visibility |
| 2a09:dd80:a::/48 | No ROA | RIR databaseRIPE | 633 100% |
| 2a09:dd80:b::/48 | No ROA | RIR databaseRIPE | 633 100% |
| 2a09:dd80::/32 | No ROA | RIR databaseRADB, RIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS209866: AS209866:AS-VORT. 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 (AS209866 isn't in the set, or no route object for AS209866 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 | AS209866 in it | Not covered |
|---|---|---|---|---|---|
| AS209866:AS-VORT | RIPE | 1 | 1 | Yes | 2 |
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 9 are in fix.csv.
- ROA: origin1
- ROA: none4
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 201.3.121.0/24 | ROAs covering it name AS218537, not AS209866. If AS209866 should announce it, add a ROA for AS209866. |
| Route object: none | 201.3.121.0/24 | Route objects for it name AS218537. Add a route object with origin AS209866 in the RIR database for the space. |
| ROA: none | 201.3.120.0/23 | No ROA covers it. Add a ROA for AS209866, maxLength 23. |
| Route object: none | 201.3.120.0/23 | No route object for it. Add a route object with origin AS209866 in the RIR database for the space. |
| ROA: none | 2a09:dd80:a::/48 | No ROA covers it. Add a ROA for AS209866, maxLength 48. |
| ROA: none | 2a09:dd80:b::/48 | No ROA covers it. Add a ROA for AS209866, maxLength 48. |
| ROA: none | 2a09:dd80::/32 | No ROA covers it. Add a ROA for AS209866, maxLength 32. |
Route objects not announced
Route objects with origin AS209866 whose prefix no peer sees AS209866 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a09:dd80:1::/48 | RIPE | No ROA |
| 2a09:dd81::/32 | 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.