asn.dev

Observed topology

AS34270 INETC Internet Connections Ltd

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS34270: 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
AS2914NTT America, Inc.TransitIPv4 IPv637
AS174Cogent Communications, LLCTransitIPv4 IPv629
AS6939Hurricane Electric LLCTransitIPv48
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS50304Blix Solutions ASUnclassifiedIPv42
AS3216PJSC "Vimpelcom"MobileIPv41
AS3741Dimension DataUnclassifiedIPv41
AS4657StarHub LtdResidentialIPv41
AS12552GlobalConnect ABUnclassifiedIPv41
AS12779IT.Gate S.p.A.UnclassifiedIPv41

All 18 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51059Brightbox Systems LtdUnclassifiedIPv4 IPv6125

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS51059Brightbox Systems LtdUnclassifiedIPv4 IPv6125
AS2914NTT America, Inc.TransitIPv4 IPv678
AS174Cogent Communications, LLCTransitIPv4 IPv663
AS6939Hurricane Electric LLCTransitIPv431
AS50304Blix Solutions ASUnclassifiedIPv47
AS34549meerfarbig GmbH & Co. KGHostingIPv46
AS3741Dimension DataUnclassifiedIPv45
AS37100SEACOM LimitedUnclassifiedIPv45
AS3216PJSC "Vimpelcom"MobileIPv42
AS4657StarHub LtdResidentialIPv42

All 19 adjacent →

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.