Network 2a05:f480:2c00::/38


Network Information

Prefix2a05:f480:2c00::/38
Announced As2a05:f480::/29
Origin ASAS20473
RPKI StatusVALID
RegistryRADB
Created2026-01-14
Last Modified2026-01-14
199524150000759424971374096939520754954463927129958511571525232020982314537174645316808551204732a05:f480:2c00::/38BGP Paths to 2a05:f480:2c00::/3813 paths from 1 origin AS

AS Looking Glass

BGP paths to 2a05:f480:2c00::/38 (origin on the right, matching graph above)

All 14 BGP Paths

Complete list of all observed paths (origin on the right)

Hostnames in this Network

Hostnames in AS

Raw WHOIS Data
route6: 2a05:f480::/29 descr: Customer Prefix origin: AS20473 notify: netops@vultr.com mnt-by: MAINT-AS20473 source: RADB changed: tlynch@vultr.com 20260114 # 21:42 GMT last-modified: 2026-01-14T21:42:10Z rpki-ov-state: valid route6: 2a05:f480::/29 origin: AS20473 descr: Vultr Assigned Prefix mnt-by: MAINT-AS20473 created: 2026-01-14T21:37:17Z last-modified: 2026-01-14T21:37:17Z source: RIPE remarks: **************************** remarks: * THIS OBJECT IS MODIFIED remarks: * Please note that all data that is generally regarded as personal remarks: * data has been removed from this object. remarks: * To view the original object, please query the RIPE Database at: remarks: * http://www.ripe.net/whois remarks: **************************** rpki-ov-state: valid route6: 2a05:f480:2c00::/38 descr: Customer Route origin: AS20473 notify: netops@vultr.com mnt-by: MAINT-AS20473 source: RADB changed: tlynch@vultr.com 20260112 # 22:14 GMT last-modified: 2026-01-12T22:15:31Z rpki-ov-state: valid route6: 2a05:f480:2c00::/38 origin: AS20473 created: 2023-04-06T18:38:31Z last-modified: 2023-04-06T18:38:31Z source: RIPE mnt-by: MAINT-AS20473 remarks: **************************** remarks: * THIS OBJECT IS MODIFIED remarks: * Please note that all data that is generally regarded as personal remarks: * data has been removed from this object. remarks: * To view the original object, please query the RIPE Database at: remarks: * http://www.ripe.net/whois remarks: **************************** rpki-ov-state: valid