Observed topology
AS8585 INTERNET-CG
Residential RIPE
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5391 | Hrvatski Telekom d.d. | Residential | IPv4 IPv6 | 944 |
Transit
Downstream networks
Networks for which AS8585 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57388 | Telecom Sh.p.k. | Unclassified | IPv4 IPv6 | 954 |
| AS39611 | Tibo Communications Sh.p.k | Residential | IPv4 | 682 |
| AS204894 | Ezmir Kraja trading as StyleNet | Unclassified | IPv4 IPv6 | 99 |
| AS47451 | Podgorica | Unclassified | IPv4 IPv6 | 72 |
| AS41439 | MAXCOM sh.p.k. | Unclassified | IPv4 IPv6 | 61 |
| AS50973 | Vodafone Albania Sh.A. | Unclassified | IPv4 | 44 |
| AS200276 | ASP Co d.o.o | Unclassified | IPv4 | 38 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8585 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5391 | Hrvatski Telekom d.d. | Residential | IPv4 IPv6 | 3,347 |
| AS57388 | Telecom Sh.p.k. | Unclassified | IPv4 IPv6 | 1,047 |
| AS39611 | Tibo Communications Sh.p.k | Residential | IPv4 IPv6 | 749 |
| AS50973 | Vodafone Albania Sh.A. | Unclassified | IPv4 IPv6 | 212 |
| AS200276 | ASP Co d.o.o | Unclassified | IPv4 | 114 |
| AS204894 | Ezmir Kraja trading as StyleNet | Unclassified | IPv4 IPv6 | 99 |
| AS41439 | MAXCOM sh.p.k. | Unclassified | IPv4 IPv6 | 84 |
| AS47451 | Podgorica | Unclassified | IPv4 IPv6 | 72 |
| AS29453 | Crnogorski Telekom a.d.Podgorica | Unclassified | IPv4 | 26 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.