asn.dev

Observed topology

AS3367 F6NET

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3367: 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 IPv6533
AS22995Xplore Inc.UnclassifiedIPv4 IPv665
AS1403EBOXResidentialIPv4 IPv622
AS22652Videotron LteeResidentialIPv4 IPv619

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29907Cirrus9 Inc.UnclassifiedIPv4326
AS21722Quick Service Software Inc.UnclassifiedIPv463
AS30657The Power Commission of The City of Saint JohnUnclassifiedIPv452
AS395386The City of MonctonUnclassifiedIPv441
AS400263NetAdmins IncUnclassifiedIPv441
AS33230Cross Country TV LtdUnclassifiedIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6998
AS29907Cirrus9 Inc.UnclassifiedIPv4326
AS22995Xplore Inc.UnclassifiedIPv4 IPv698
AS21722Quick Service Software Inc.UnclassifiedIPv463
AS30657The Power Commission of The City of Saint JohnUnclassifiedIPv452
AS1403EBOXResidentialIPv4 IPv644
AS22652Videotron LteeResidentialIPv4 IPv643
AS395386The City of MonctonUnclassifiedIPv441
AS400263NetAdmins IncUnclassifiedIPv441
AS33230Cross Country TV LtdUnclassifiedIPv4 IPv621

Provenance

Where this comes from

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