asn.dev

Observed topology

AS34295 ETA-BG-ASN

Mobile RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34295: 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
AS8866Vivacom Bulgaria EADResidentialIPv46,518
AS41313"NOVATEL" EOODUnclassifiedIPv42,115
AS34224Neterra Ltd.UnclassifiedIPv4180

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48747Lukovitnet Ltd.UnclassifiedIPv4806
AS208860North West Union Ltd.UnclassifiedIPv416

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8866Vivacom Bulgaria EADResidentialIPv47,341
AS41313"NOVATEL" EOODUnclassifiedIPv42,115
AS48747Lukovitnet Ltd.UnclassifiedIPv4807
AS34224Neterra Ltd.UnclassifiedIPv4180
AS208860North West Union Ltd.UnclassifiedIPv416

Provenance

Where this comes from

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