asn.dev

Observed topology

AS208398 TELETECH Edge Technology Plus d.o.o. Beograd

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208398: 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
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6854
AS1299Arelion Sweden ABTransitIPv4 IPv6536
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6370
AS174Cogent Communications, LLCTransitIPv4 IPv6268

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215013Yandex.Cloud LLCUnclassifiedIPv4151
AS215024Direct Cursus Technology LLCUnclassifiedIPv4 IPv691
AS207304Y. Izdeu men Jarnama LLPUnclassifiedIPv4 IPv665
AS212066Buyuk Reklam Cozumleri LLCUnclassifiedIPv4 IPv663

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6962
AS1299Arelion Sweden ABTransitIPv4 IPv6632
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6482
AS174Cogent Communications, LLCTransitIPv4 IPv6322
AS215013Yandex.Cloud LLCUnclassifiedIPv4151
AS215024Direct Cursus Technology LLCUnclassifiedIPv4 IPv691
AS207304Y. Izdeu men Jarnama LLPUnclassifiedIPv4 IPv665
AS212066Buyuk Reklam Cozumleri LLCUnclassifiedIPv4 IPv663

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.