Observed topology

AS205714 tele2hr Telemach Hrvatska d.o.o.

Unclassified RIPE

Upstreams 3 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 14

Adjacent (IPv6) 3

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS205714: 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
AS3212	Telemach Slovenija d.o.o.	Residential	IPv4	861
AS6939	Hurricane Electric LLC	Transit	IPv6	35
AS21215	UNITED GROUP NETWORK INFRASTRUCTURE d.o.o. Beograd	Residential	IPv4	23

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS34594	Telemach Hrvatska d.o.o.	Unclassified	IPv4 IPv6	1,076
AS34748	Telemach Hrvatska d.o.o.	Unclassified	IPv4	64
AS48797	Odasiljaci i veze d.o.o.	Unclassified	IPv4	18
AS199106	Mireo d.d.	Unclassified	IPv4	8
AS25467	Akton d.o.o.	Unclassified	IPv4	3
AS211619	MAXKO d.o.o.	Hosting	IPv4	3

Adjacency

Adjacent networks

All 14

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

AS	Network	Type	Families	Paths seen
AS34594	Telemach Hrvatska d.o.o.	Unclassified	IPv4 IPv6	2,842
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	1,733
AS3212	Telemach Slovenija d.o.o.	Residential	IPv4	1,253
AS21215	UNITED GROUP NETWORK INFRASTRUCTURE d.o.o. Beograd	Residential	IPv4 IPv6	560
AS174	Cogent Communications, LLC	Transit	IPv4	256
AS3356	Level 3 Parent, LLC	Transit	IPv4	122
AS34748	Telemach Hrvatska d.o.o.	Unclassified	IPv4	64
AS5391	Hrvatski Telekom d.d.	Residential	IPv4	62
AS48797	Odasiljaci i veze d.o.o.	Unclassified	IPv4	18
AS199106	Mireo d.d.	Unclassified	IPv4	8

All 14 adjacent →

Provenance

Where this comes from

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