asn.dev

Observed topology

AS34187 RENOME-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34187: 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 LLCTransitIPv4 IPv6533
AS9002RETN LimitedUnclassifiedIPv4 IPv6120
AS35297Dataline LLCUnclassifiedIPv444
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv624
AS3255LLC EKSINTECHUnclassifiedIPv412
AS24482SG.GSHostingIPv4 IPv612
AS44600"GIGATRANS UKRAINE", LLCUnclassifiedIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31593TV Company "Black Sea" LtdUnclassifiedIPv4 IPv6280
AS15713LLC Global-City-NetUnclassifiedIPv4184
AS197192Private Enterprise KTV AIDAUnclassifiedIPv465
AS42798Sergey Vyacheslavovich GligaResidentialIPv440
AS57962LLC " Ug telekom grup "UnclassifiedIPv439

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,152
AS31593TV Company "Black Sea" LtdUnclassifiedIPv4 IPv6415
AS15713LLC Global-City-NetUnclassifiedIPv4212
AS9002RETN LimitedUnclassifiedIPv4 IPv6181
AS35297Dataline LLCUnclassifiedIPv4123
AS57962LLC " Ug telekom grup "UnclassifiedIPv478
AS197192Private Enterprise KTV AIDAUnclassifiedIPv465
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4 IPv644
AS42798Sergey Vyacheslavovich GligaResidentialIPv440
AS3255LLC EKSINTECHUnclassifiedIPv436

All 12 adjacent →

Provenance

Where this comes from

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