asn.dev

Observed topology

AS43940 MTEL-AS Drustvo za telekomunikacije "MTEL" DOO

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43940: 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
AS8400TELEKOM SRBIJA a.d.ResidentialIPv4 IPv63,877

Transit

Downstream networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS198961Orion Telekom Tim d.o.o.BeogradUnclassifiedIPv4915
AS201649Centralna Banka Crne GoreUnclassifiedIPv4242
AS57070ITCOM ShpkUnclassifiedIPv4 IPv6138
AS62301IPMONT d.o.o. PodgoricaUnclassifiedIPv4102
AS209302Bujar ShimajUnclassifiedIPv454
AS47451PodgoricaUnclassifiedIPv429
AS200276ASP Co d.o.oUnclassifiedIPv429
AS40981University of MontenegroUnclassifiedIPv410
AS203824Info Sistemi d.o.o.UnclassifiedIPv45
AS202644Wireless Montenegro D.O.O.UnclassifiedIPv43

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS8400TELEKOM SRBIJA a.d.ResidentialIPv4 IPv65,524
AS198961Orion Telekom Tim d.o.o.BeogradUnclassifiedIPv4915
AS201649Centralna Banka Crne GoreUnclassifiedIPv4242
AS200276ASP Co d.o.oUnclassifiedIPv4148
AS57070ITCOM ShpkUnclassifiedIPv4 IPv6138
AS62301IPMONT d.o.o. PodgoricaUnclassifiedIPv4102
AS209302Bujar ShimajUnclassifiedIPv454
AS47451PodgoricaUnclassifiedIPv429
AS40981University of MontenegroUnclassifiedIPv410
AS203824Info Sistemi d.o.o.UnclassifiedIPv45

Provenance

Where this comes from

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