asn.dev

Observed topology

AS33983 ARTMOTION-AS

Unclassified APNIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33983: 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 IPv61,823
AS6939Hurricane Electric LLCTransitIPv4866
AS174Cogent Communications, LLCTransitIPv4243

Transit

Downstream networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS29170Kujtesa Net Sh.p.k.UnclassifiedIPv4765
AS43272DOTNET SH.P.KResidentialIPv4688
AS203675VISTA SH.P.K.UnclassifiedIPv4325
AS204285OPTIMUM Telecommunications LLCUnclassifiedIPv4192
AS211468KOSNET Telecommunications LLCUnclassifiedIPv4140
AS208286Max tv SH. P. KUnclassifiedIPv465
AS210740ATM Fiber SH.P.KUnclassifiedIPv464
AS211555NET"UnclassifiedIPv464
AS208734ELSA-TECH SH.P.K.UnclassifiedIPv458
AS51404EULEX KosovoUnclassifiedIPv452

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv42,486
AS8400TELEKOM SRBIJA a.d.ResidentialIPv4 IPv62,014
AS174Cogent Communications, LLCTransitIPv4946
AS29170Kujtesa Net Sh.p.k.UnclassifiedIPv4783
AS43272DOTNET SH.P.KResidentialIPv4688
AS203675VISTA SH.P.K.UnclassifiedIPv4325
AS204285OPTIMUM Telecommunications LLCUnclassifiedIPv4192
AS211468KOSNET Telecommunications LLCUnclassifiedIPv4140
AS208286Max tv SH. P. KUnclassifiedIPv465
AS210740ATM Fiber SH.P.KUnclassifiedIPv464

Provenance

Where this comes from

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