asn.dev

Observed topology

AS45691 DODO-CHIBA DODO K.K.

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45691: 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
AS174Cogent Communications, LLCTransitIPv4909
AS6939Hurricane Electric LLCTransitIPv4 IPv6653
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4583
AS24482SG.GSHostingIPv4 IPv643
AS17639Converge ICT Solutions Inc.UnclassifiedIPv432
AS20485Joint Stock Company TransTeleComUnclassifiedIPv432
AS48266Catixs LtdUnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63801DODO K.K.ResidentialIPv4232
AS38647NEI's NetLabUnclassifiedIPv458
AS49671DODO K.K.UnclassifiedIPv457
AS9743Nippon EDUIXUnclassifiedIPv637
AS9786XIANDOUCLOUD INFORMATION TECHNOLOGY LTDUnclassifiedIPv637
AS17626Yasuda Network LTDUnclassifiedIPv637
AS150413Huang WeilongUnclassifiedIPv637

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4982
AS6939Hurricane Electric LLCTransitIPv4 IPv6834
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4743
AS63801DODO K.K.ResidentialIPv4232
AS48266Catixs LtdUnclassifiedIPv466
AS38647NEI's NetLabUnclassifiedIPv458
AS49671DODO K.K.UnclassifiedIPv457
AS24482SG.GSHostingIPv4 IPv652
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv641
AS9743Nippon EDUIXUnclassifiedIPv637

Provenance

Where this comes from

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