Network · data from 2026-11-12
AS50219 VT-255-50219 - Valence Technology Co.
Registry name: VT-255-50219 - Valence Technology Co., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50219, 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.
| 216.226.77.0/24 | No ROA | Nonecovered by 216.226.76.0/22 | 670 100% |
| 2602:f71d:200::/48 | No ROA | Nonecovered by 2602:f71d::/36 | 635 100% |
| 216.226.76.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 194.164.107.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2602:f71d::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 216.226.78.0/24 | No ROA | RIR databaseARIN | 662 98% |
| 2602:f71d:400::/48 | No ROA | RIR databaseARIN | 636 100% |
AS-SET
AS50219 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 15 are in fix.csv.
- ROA: none7
- Route object: none2
- Route object: RIR3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.226.77.0/24 | No ROA covers it. Add a ROA for AS50219, maxLength 24. |
| Route object: none | 216.226.77.0/24 | No route object for it. A route object for 216.226.76.0/22 with origin AS50219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50219 in the RIR database for the space. |
| ROA: none | 2602:f71d:200::/48 | No ROA covers it. Add a ROA for AS50219, maxLength 48. |
| Route object: none | 2602:f71d:200::/48 | No route object for it. A route object for 2602:f71d::/36 with origin AS50219 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50219 in the RIR database for the space. |
| ROA: none | 216.226.76.0/24 | No ROA covers it. Add a ROA for AS50219, maxLength 24. |
| Route object: RIR | 216.226.76.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 194.164.107.0/24 | No ROA covers it. Add a ROA for AS50219, maxLength 24. |
| Route object: RIR | 194.164.107.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2602:f71d::/48 | No ROA covers it. Add a ROA for AS50219, maxLength 48. |
| Route object: RIR | 2602:f71d::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 216.226.78.0/24 | No ROA covers it. Add a ROA for AS50219, maxLength 24. |
| ROA: none | 2602:f71d:400::/48 | No ROA covers it. Add a ROA for AS50219, maxLength 48. |
Route objects not announced
Route objects with origin AS50219 whose prefix no peer sees AS50219 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.55.131.0/24 | RADB | No ROA |
| 216.226.76.0/22 | ARIN | No ROA |
| 2602:f71d::/36 | ARIN | 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.