Observed topology
AS5391 T-HT Hrvatski Telekom d.d.
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS5391: 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 |
|---|---|---|---|---|
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 973 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 612 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 513 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 384 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 229 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 109 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 16 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 11 |
Transit
Downstream networks
Networks for which AS5391 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS13046 | Hrvatski Telekom d.d. | Residential | IPv4 IPv6 | 21,403 |
| AS9146 | BH Telecom d.d. Sarajevo | Residential | IPv4 IPv6 | 2,441 |
| AS20875 | JP HT d.d. Mostar | Unclassified | IPv4 | 2,210 |
| AS25144 | "Telekomunikacije Republike Srpske" akcionarsko drustvo Banja Luka | Unclassified | IPv4 IPv6 | 1,230 |
| AS8585 | Crnogorski Telekom a.d.Podgorica | Residential | IPv4 IPv6 | 943 |
| AS203463 | ASEE SOLUTIONS d.o.o | Unclassified | IPv4 | 246 |
| AS35567 | DASTO semtel d.o.o. | Unclassified | IPv4 | 177 |
| AS9119 | SOFTNET d.o.o. | Residential | IPv4 | 158 |
| AS44377 | MAGIC NET D.O.O. | Unclassified | IPv4 | 150 |
| AS214427 | Netvis d.o.o. | Unclassified | IPv4 IPv6 | 149 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5391 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS13046 | Hrvatski Telekom d.d. | Residential | IPv4 IPv6 | 21,996 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 15,188 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 12,816 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 7,402 |
| AS9146 | BH Telecom d.d. Sarajevo | Residential | IPv4 IPv6 | 6,592 |
| AS20875 | JP HT d.d. Mostar | Unclassified | IPv4 | 5,489 |
| AS25144 | "Telekomunikacije Republike Srpske" akcionarsko drustvo Banja Luka | Unclassified | IPv4 IPv6 | 5,101 |
| AS8585 | Crnogorski Telekom a.d.Podgorica | Residential | IPv4 IPv6 | 3,310 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 3,251 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,103 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.