AS50219 Valence Technology Co.
AS50219 (VT-255-50219) is registered to Valence Technology Co. in US, through RIPE. It originates 7 prefixes in the global routing table.
Who holds AS50219
Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.
WHOIS recordRIPE
% This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See https://docs.db.ripe.net/terms-conditions.html % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to 'AS50219 - AS50219' as-block: AS50219 - AS50219 descr: ASN block not managed by the RIPE NCC remarks: ------------------------------------------------------ remarks: remarks: aut-num objects within this block represent routing remarks: policy published in the RIPE Database remarks: remarks: For registration information, remarks: you can find the whois server to query, or the remarks: IANA registry to query on this web page: remarks: http://www.iana.org/assignments/ipv4-address-space remarks: remarks: You can access databases of other RIR's at: remarks: remarks: AFRINIC (Africa) remarks: http://www.afrinic.net/ whois.afrinic.net remarks: remarks: APNIC (Asia Pacific) remarks: http://www.apnic.net/ whois.apnic.net remarks: remarks: ARIN (Northern America) remarks: http://www.arin.net/ whois.arin.net remarks: remarks: LACNIC (Latin America and the Carribean) remarks: http://www.lacnic.net/ whois.lacnic.net remarks: remarks: ------------------------------------------------------ mnt-by: RIPE-DBM-MNT created: 2024-03-26T14:48:18Z last-modified: 2024-03-26T14:48:18Z source: RIPE % This query was served by the RIPE Database Query Service version 1.124.1 (SHETLAND)
What AS50219 announces
Prefixes originated by AS50219 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).
Announced prefixes
Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.
RPKI valid RPKI invalid no ROA covers it
Who AS50219 is reached through
The AS just before AS50219 in the paths our looking glass collectors hold, for 7 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.
Routing registry objects
From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.
Route objects with origin AS50219: ARIN 4 · RADB 4