asn.dev

Observed topology

AS134666 HoshiNetwork - Hoshi Network

Unclassified APNIC Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS134666: 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
AS212027PebbleHost LtdHostingIPv6106
AS34927iFog GmbHHostingIPv699
AS20473The Constant Company, LLCHostingIPv693
AS6939Hurricane Electric LLCTransitIPv636
AS37988Alpha Layer Pty LtdUnclassifiedIPv636
AS205794JINZE YANGUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209556Benli ZhongUnclassifiedIPv636

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv6135
AS212027PebbleHost LtdHostingIPv6106
AS20473The Constant Company, LLCHostingIPv693
AS6939Hurricane Electric LLCTransitIPv636
AS37988Alpha Layer Pty LtdUnclassifiedIPv636
AS209556Benli ZhongUnclassifiedIPv636
AS205794JINZE YANGUnclassifiedIPv62

Provenance

Where this comes from

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