Network · data from 2026-11-12
AS50173 VTESSE GTT - EMEA Ltd.
Registry name: VTESSE GTT - EMEA Ltd., GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50173, 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.
| 2a00:16c8:110::/48 | No ROA | Nonecovered by 2a00:16c8::/32 | 635 100% |
| 2a00:16c8:111::/48 | No ROA | Nonecovered by 2a00:16c8::/32 | 635 100% |
| 80.82.134.0/24 | No ROA | Nonecovered by 80.82.128.0/20 | 2 0%low visibility |
| 80.82.135.0/24 | No ROA | Nonecovered by 80.82.128.0/20 | 2 0%low visibility |
| 80.82.132.0/24 | No ROA | Nonecovered by 80.82.128.0/20 | 1 0%low visibility |
| 80.82.133.0/24 | No ROA | Nonecovered by 80.82.128.0/20 | 1 0%low visibility |
AS-SET
AS50173 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: none6
- Route object: none6
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a00:16c8:110::/48 | No ROA covers it. Add a ROA for AS50173, maxLength 48. |
| Route object: none | 2a00:16c8:110::/48 | No route object for it. A route object for 2a00:16c8::/32 with origin AS50173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50173 in the RIR database for the space. |
| ROA: none | 2a00:16c8:111::/48 | No ROA covers it. Add a ROA for AS50173, maxLength 48. |
| Route object: none | 2a00:16c8:111::/48 | No route object for it. A route object for 2a00:16c8::/32 with origin AS50173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50173 in the RIR database for the space. |
| ROA: none | 80.82.134.0/24 | No ROA covers it. Add a ROA for AS50173, maxLength 24. |
| Route object: none | 80.82.134.0/24 | No route object for it. A route object for 80.82.128.0/20 with origin AS50173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50173 in the RIR database for the space. |
| ROA: none | 80.82.135.0/24 | No ROA covers it. Add a ROA for AS50173, maxLength 24. |
| Route object: none | 80.82.135.0/24 | No route object for it. A route object for 80.82.128.0/20 with origin AS50173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50173 in the RIR database for the space. |
| ROA: none | 80.82.132.0/24 | No ROA covers it. Add a ROA for AS50173, maxLength 24. |
| Route object: none | 80.82.132.0/24 | No route object for it. A route object for 80.82.128.0/20 with origin AS50173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50173 in the RIR database for the space. |
| ROA: none | 80.82.133.0/24 | No ROA covers it. Add a ROA for AS50173, maxLength 24. |
| Route object: none | 80.82.133.0/24 | No route object for it. A route object for 80.82.128.0/20 with origin AS50173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50173 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS50173 whose prefix no peer sees AS50173 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.82.128.0/20 | RIPE | No ROA |
| 109.71.168.0/21 | RIPE | No ROA |
| 149.126.104.0/21 | RIPE | No ROA |
| 185.4.164.0/22 | RIPE | No ROA |
| 2a00:16c8::/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.