asn.dev

Observed topology

AS44302 IECHU-AS

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44302: 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 LLCTransitIPv4110
AS3257GTT Communications Inc.TransitIPv420
AS33891Core-Backbone GmbHHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39201WaveCom Informatikai Kft.UnclassifiedIPv4304
AS48893ESO TV Kft.UnclassifiedIPv466
AS196970Langaton Hungary KftUnclassifiedIPv448

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4613
AS39201WaveCom Informatikai Kft.UnclassifiedIPv4456
AS3257GTT Communications Inc.TransitIPv483
AS48893ESO TV Kft.UnclassifiedIPv466
AS196970Langaton Hungary KftUnclassifiedIPv448
AS33891Core-Backbone GmbHHostingIPv46

Provenance

Where this comes from

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