asn.dev

Observed topology

AS394453 ITO-DG

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS394453: 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
AS19229Ensono LPUnclassifiedIPv4420
AS6939Hurricane Electric LLCTransitIPv4168
AS3356Level 3 Parent, LLCTransitIPv427

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS395339Donnelley Financial, LLC.UnclassifiedIPv4878
AS14328R.R. Donnelley and Sons, Co.UnclassifiedIPv4660

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS19229Ensono LPUnclassifiedIPv41,080
AS395339Donnelley Financial, LLC.UnclassifiedIPv4878
AS6939Hurricane Electric LLCTransitIPv4702
AS14328R.R. Donnelley and Sons, Co.UnclassifiedIPv4660
AS198949Radware LtdUnclassifiedIPv4286
AS3356Level 3 Parent, LLCTransitIPv485

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.