Observed topology

AS34540 MSTART-AS

Unclassified ARIN

Upstreams 2 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

Upstream graph Who carries AS34540, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS34540 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34540: 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.

AS	Network	Type	Families	Paths seen
AS13046	Hrvatski Telekom d.d.	Residential	IPv4	58
AS61211	SETCOR d.o.o.	Unclassified	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS43784	Mercator-S d.o.o.	Unclassified	IPv4	60
AS43953	mStart plus d.o.o.	Unclassified	IPv4	60
AS48059	Konzum d.o.o. Sarajevo	Unclassified	IPv4	60
AS51434	MERCATOR-CG DOO Podgorica	Unclassified	IPv4	59
AS39689	Konzum d.o.o. Sarajevo	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS13046	Hrvatski Telekom d.d.	Residential	IPv4	285
AS61211	SETCOR d.o.o.	Unclassified	IPv4	71
AS43784	Mercator-S d.o.o.	Unclassified	IPv4	60
AS43953	mStart plus d.o.o.	Unclassified	IPv4	60
AS48059	Konzum d.o.o. Sarajevo	Unclassified	IPv4	60
AS51434	MERCATOR-CG DOO Podgorica	Unclassified	IPv4	59
AS39689	Konzum d.o.o. Sarajevo	Unclassified	IPv4	58

Provenance

Where this comes from

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