Observed topology

AS62844 SEIMITSU

Unclassified ARIN Cable/DSL/ISP

Upstreams 4 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS62844: 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	778
AS174	Cogent Communications, LLC	Transit	IPv4	210
AS6461	Zayo Bandwidth	Transit	IPv4	22
AS31877	Accelecom	Residential	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS3480	Board of Regents of the University System of Georgia	Education	IPv4	187
AS54998	St. Josephs/Candler Health System, Inc.	Unclassified	IPv4	40

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	1,753
AS3480	Board of Regents of the University System of Georgia	Education	IPv4	1,237
AS174	Cogent Communications, LLC	Transit	IPv4	553
AS35280	F5 Networks SARL	Hosting	IPv4	46
AS54998	St. Josephs/Candler Health System, Inc.	Unclassified	IPv4	40
AS6461	Zayo Bandwidth	Transit	IPv4	27
AS31877	Accelecom	Residential	IPv4	2

Provenance

Where this comes from

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