asn.dev

Observed topology

AS62246 WJY-AS WJY Limited

Residential RIPE

Upstreams 19 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 19
Adjacent (IPv6) 10
Upstream graph Who carries AS62246, and who carries them, drawn as a map up to the transit-free core. 5 exchanges Where AS62246 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS62246: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6168
AS174Cogent Communications, LLCTransitIPv4 IPv693
AS16276OVH SASHostingIPv461
AS53808MoeDoveUnclassifiedIPv445
AS6204INTERKVM HOST SRLUnclassifiedIPv441
AS17433Hytron Network Services LimitedResidentialIPv437
AS213605Liu HaoRanUnclassifiedIPv636
AS24482SG.GSHostingIPv4 IPv68
AS9002RETN LimitedUnclassifiedIPv46
AS27523Kawaii Networks LLCUnclassifiedIPv46

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197752Asia Core LimitedUnclassifiedIPv4170
AS199592WAHYUHostingIPv4 IPv6130
AS47778Sunoaki Network LLCUnclassifiedIPv631

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6314
AS197752Asia Core LimitedUnclassifiedIPv4170
AS174Cogent Communications, LLCTransitIPv4 IPv6139
AS199592WAHYUHostingIPv4 IPv6130
AS17433Hytron Network Services LimitedResidentialIPv4111
AS6204INTERKVM HOST SRLUnclassifiedIPv481
AS16276OVH SASHostingIPv461
AS53808MoeDoveUnclassifiedIPv445
AS213605Liu HaoRanUnclassifiedIPv636
AS47778Sunoaki Network LLCUnclassifiedIPv631

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.