Observed topology

AS44143 A1SERBIA-AS

Unclassified RIPE

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

Upstream graph Who carries AS44143, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS44143 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44143: 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
AS8447	A1 Telekom Austria AG	Residential	IPv4 IPv6	975
AS1299	Arelion Sweden AB	Transit	IPv6	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS62012	Generali Osiguranje Srbija	Unclassified	IPv4	120
AS394977	TAKE-TWO INTERACTIVE SOFTWARE, INC.	Unclassified	IPv4	45
AS205201	Public Service Media Radio Television of Serbia	Unclassified	IPv4	1
AS213008	APOTEKARSKA USTANOVA LILLY DROGERIE BEOGRAD	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS8447	A1 Telekom Austria AG	Residential	IPv4 IPv6	1,144
AS62012	Generali Osiguranje Srbija	Unclassified	IPv4	120
AS394977	TAKE-TWO INTERACTIVE SOFTWARE, INC.	Unclassified	IPv4	45
AS1299	Arelion Sweden AB	Transit	IPv6	32
AS31042	Yettel d.o.o.	Residential	IPv4	2
AS205201	Public Service Media Radio Television of Serbia	Unclassified	IPv4	1
AS213008	APOTEKARSKA USTANOVA LILLY DROGERIE BEOGRAD	Unclassified	IPv4	1

Provenance

Where this comes from

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