asn.dev

Observed topology

AS3663 NETNET-NET - NetNet

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 AS3663, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS3663 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3663: 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 IPv61,438
AS6461Zayo BandwidthTransitIPv4 IPv6953
AS174Cogent Communications, LLCTransitIPv4 IPv6620
AS24482SG.GSHostingIPv4 IPv649

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397463Washington Island Electric Cooperative, Inc.UnclassifiedIPv4 IPv6198
AS398370Northwoods ConnectUnclassifiedIPv4124
AS7268Athenet Internet ServicesUnclassifiedIPv4119
AS394660Chequamegon Communications Cooperative, Inc.UnclassifiedIPv4102
AS395091Plexus Corp.UnclassifiedIPv463
AS12081Greenheck FanUnclassifiedIPv446

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,808
AS6461Zayo BandwidthTransitIPv4 IPv61,133
AS174Cogent Communications, LLCTransitIPv4 IPv6712
AS397463Washington Island Electric Cooperative, Inc.UnclassifiedIPv4 IPv6198
AS398370Northwoods ConnectUnclassifiedIPv4124
AS7268Athenet Internet ServicesUnclassifiedIPv4119
AS394660Chequamegon Communications Cooperative, Inc.UnclassifiedIPv4102
AS395091Plexus Corp.UnclassifiedIPv463
AS24482SG.GSHostingIPv4 IPv659
AS12081Greenheck FanUnclassifiedIPv446

Provenance

Where this comes from

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