asn.dev

Observed topology

AS912 HUT8-EAST

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS912: 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
AS6461Zayo BandwidthTransitIPv4 IPv61,655
AS6327Shaw CommunicationsResidentialIPv4 IPv6526
AS812Rogers Communications Canada Inc.MobileIPv4 IPv6475
AS20161TeraGo Networks Inc.UnclassifiedIPv4182

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS30406Think On, Inc.UnclassifiedIPv4232
AS63278Carillon Information Security Inc.UnclassifiedIPv460
AS63372WEBSAN SOLUTIONS INCUnclassifiedIPv459
AS13804ATG Arrow Technology Group Limited PartnershipUnclassifiedIPv458
AS401750IT Solutions Consulting, LLCUnclassifiedIPv420

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,964
AS812Rogers Communications Canada Inc.MobileIPv4 IPv6632
AS6327Shaw CommunicationsResidentialIPv4 IPv6547
AS30406Think On, Inc.UnclassifiedIPv4232
AS20161TeraGo Networks Inc.UnclassifiedIPv4182
AS63278Carillon Information Security Inc.UnclassifiedIPv460
AS63372WEBSAN SOLUTIONS INCUnclassifiedIPv459
AS13804ATG Arrow Technology Group Limited PartnershipUnclassifiedIPv458
AS13826TeraGo Networks Inc.UnclassifiedIPv458
AS401750IT Solutions Consulting, LLCUnclassifiedIPv420

Provenance

Where this comes from

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