asn.dev

Observed topology

AS40028 AS40028 - 1651884 Ontario Inc.

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40028: 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
AS1299Arelion Sweden ABTransitIPv41,437
AS3257GTT Communications Inc.TransitIPv4 IPv6554
AS6939Hurricane Electric LLCTransitIPv4 IPv6471
AS1403EBOXResidentialIPv4 IPv6100
AS22652Videotron LteeResidentialIPv4 IPv699
AS24482SG.GSHostingIPv4 IPv649
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv649
AS35280F5 Networks SARLHostingIPv43
AS20473The Constant Company, LLCHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS194463Z CanadaUnclassifiedIPv4 IPv6862
AS52676C3 Desenvolvimento de Sistemas ComputacionaisUnclassifiedIPv4 IPv6146
AS3257GTT Communications Inc.TransitIPv48

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv62,077
AS194463Z CanadaUnclassifiedIPv4 IPv6976
AS3257GTT Communications Inc.TransitIPv4 IPv6892
AS6939Hurricane Electric LLCTransitIPv4 IPv6674
AS1403EBOXResidentialIPv4 IPv6192
AS22652Videotron LteeResidentialIPv4 IPv6163
AS52676C3 Desenvolvimento de Sistemas ComputacionaisUnclassifiedIPv4 IPv6146
AS22533Inquiry Management SystemsUnclassifiedIPv458
AS24482SG.GSHostingIPv4 IPv651
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv651

All 13 adjacent →

Provenance

Where this comes from

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