Observed topology

AS29319 ASN-IMSYS

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 12

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29319: 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
AS202984	Chernyshov Aleksandr Aleksandrovich	Unclassified	IPv4	362

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS42482	Informational-measuring systems Ltd.	Unclassified	IPv4	82
AS197498	VERBETA Ltd.	Unclassified	IPv4	66
AS58319	Kazakov Aleksey Dmitrievich	Unclassified	IPv4	51
AS62450	TELECOMPROEKT Ltd.	Unclassified	IPv4	47
AS50471	Limited Liability Company Sviaz Industriya	Unclassified	IPv4	8
AS43234	Chip-Telecom Ltd.	Unclassified	IPv4	3

Adjacency

Adjacent networks

All 12

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

AS	Network	Type	Families	Paths seen
AS202984	Chernyshov Aleksandr Aleksandrovich	Unclassified	IPv4	362
AS35598	INETCOM CARRIER LLC	Unclassified	IPv4	184
AS42482	Informational-measuring systems Ltd.	Unclassified	IPv4	82
AS197498	VERBETA Ltd.	Unclassified	IPv4	66
AS8641	LLC "Nauka-Svyaz"	Unclassified	IPv4	61
AS58319	Kazakov Aleksey Dmitrievich	Unclassified	IPv4	51
AS62450	TELECOMPROEKT Ltd.	Unclassified	IPv4	47
AS62255	BiMajLink d.o.o.	Unclassified	IPv4	11
AS50471	Limited Liability Company Sviaz Industriya	Unclassified	IPv4	8
AS43234	Chip-Telecom Ltd.	Unclassified	IPv4	5

All 12 adjacent →

Provenance

Where this comes from

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