Observed topology

AS396905 HOMEWORKS-1 - HomeWorks Connect

Residential ARIN Cable/DSL/ISP

Upstreams 5 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

Upstream graph Who carries AS396905, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS396905 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396905: 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	486
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	70
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	55
AS24482	SG.GS	Hosting	IPv4 IPv6	10
AS20205	Amplex Electric, Inc.	Residential	IPv4	8

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS400238	PIE&G	Unclassified	IPv4	2,449
AS63083	Chapin Long Distance, Inc.	Unclassified	IPv4	76
AS35979	WBI	Unclassified	IPv4	43

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	2,625
AS400238	PIE&G	Unclassified	IPv4	2,449
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	296
AS2914	NTT America, Inc.	Transit	IPv4 IPv6	171
AS63083	Chapin Long Distance, Inc.	Unclassified	IPv4	76
AS24482	SG.GS	Hosting	IPv4 IPv6	53
AS20205	Amplex Electric, Inc.	Residential	IPv4	52
AS35979	WBI	Unclassified	IPv4	43

Provenance

Where this comes from

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