asn.dev

Observed topology

AS216458 HardCore Hardcore Communication Co., Limited

Unclassified RIPE

Upstreams 2 carry this network
Downstreams 11 this network carries
Adjacent (IPv4) 17
Adjacent (IPv6) 2
Upstream graph Who carries AS216458, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS216458 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS216458: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS49304SAKURA LINK LIMITEDUnclassifiedIPv461
AS5068STACKS INCUnclassifiedIPv459

Transit

Downstream networks

All 11

Networks for which AS216458 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS54994Meteverse Limited.UnclassifiedIPv465
AS31972Emagine Concept, Inc.HostingIPv436
AS132369XIANGAO INTERNATIONAL TELECOMMUNICATION LIMITEDUnclassifiedIPv436
AS979NetLab GlobalHostingIPv412
AS49304SAKURA LINK LIMITEDUnclassifiedIPv46
AS396856Sharon Networks, LLCUnclassifiedIPv46
AS36002GoMami NetworksUnclassifiedIPv4 IPv63
AS9416Hoshin Multimedia Center Inc.ResidentialIPv42
AS401586Squirrel Networks LLCUnclassifiedIPv42
AS402306DataForge Technologies LLCUnclassifiedIPv42

Adjacency

Adjacent networks

All 17

Every AS seen directly next to AS216458 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS23764CTGNetUnclassifiedIPv4 IPv6161
AS49304SAKURA LINK LIMITEDUnclassifiedIPv469
AS54994Meteverse Limited.UnclassifiedIPv465
AS5068STACKS INCUnclassifiedIPv459
AS31972Emagine Concept, Inc.HostingIPv436
AS132369XIANGAO INTERNATIONAL TELECOMMUNICATION LIMITEDUnclassifiedIPv436
AS10099China Unicom GlobalUnclassifiedIPv414
AS979NetLab GlobalHostingIPv412
AS396856Sharon Networks, LLCUnclassifiedIPv46
AS36002GoMami NetworksUnclassifiedIPv4 IPv63

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.