asn.dev

Observed topology

AS34442 AMATISNETWORKS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34442: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6617
AS2914NTT America, Inc.TransitIPv4 IPv6295
AS6939Hurricane Electric LLCTransitIPv4 IPv6198
AS33891Core-Backbone GmbHHostingIPv442
AS62172AIRBYTES COMMUNICATIONS LimitedUnclassifiedIPv430
AS24482SG.GSHostingIPv4 IPv622
AS48185team.blue NVUnclassifiedIPv4 IPv622
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv622
AS25091IP-Max SAUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197758NXLayer LtdUnclassifiedIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6630
AS2914NTT America, Inc.TransitIPv4 IPv6295
AS6939Hurricane Electric LLCTransitIPv4 IPv6198
AS33891Core-Backbone GmbHHostingIPv442
AS62172AIRBYTES COMMUNICATIONS LimitedUnclassifiedIPv430
AS24482SG.GSHostingIPv4 IPv622
AS48185team.blue NVUnclassifiedIPv4 IPv622
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv622
AS197758NXLayer LtdUnclassifiedIPv413
AS25091IP-Max SAUnclassifiedIPv61

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.