asn.dev

Observed topology

AS8585 INTERNET-CG Crnogorski Telekom a.d.Podgorica

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8585: 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
AS5391Hrvatski Telekom d.d.ResidentialIPv4 IPv6929

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57388Telecom Sh.p.k.UnclassifiedIPv4 IPv6922
AS39611Tibo Communications Sh.p.kResidentialIPv4673
AS204894Ezmir Kraja trading as StyleNetUnclassifiedIPv4 IPv697
AS47451PodgoricaUnclassifiedIPv4 IPv669
AS41439MAXCOM sh.p.k.UnclassifiedIPv4 IPv658
AS200276ASP Co d.o.oUnclassifiedIPv436
AS50973Vodafone Albania Sh.A.UnclassifiedIPv427

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5391Hrvatski Telekom d.d.ResidentialIPv4 IPv63,238
AS57388Telecom Sh.p.k.UnclassifiedIPv4 IPv61,012
AS39611Tibo Communications Sh.p.kResidentialIPv4737
AS50973Vodafone Albania Sh.A.UnclassifiedIPv4 IPv6185
AS200276ASP Co d.o.oUnclassifiedIPv4108
AS204894Ezmir Kraja trading as StyleNetUnclassifiedIPv4 IPv697
AS41439MAXCOM sh.p.k.UnclassifiedIPv4 IPv676
AS47451PodgoricaUnclassifiedIPv4 IPv669
AS29453Crnogorski Telekom a.d.PodgoricaUnclassifiedIPv425

Provenance

Where this comes from

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