Observed topology

AS3218 COSMOS-3218-AS AS-COSMOS root

Unclassified RIPE

Upstreams 1 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3218: 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
AS12722	RECONN LLC	Hosting	IPv4	1,464

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS5386	Federal State Budgetary Institution of Science "Space Research Institute of the Russian Academy of Sciences".	Unclassified	IPv4	366
AS49834	Best Hosting Company, LLC	Unclassified	IPv4	305
AS49554	P.P.Shirshov Institute of Oceanology RAS	Unclassified	IPv4	114
AS34849	Federal State Institution of Higher Professional Education "Peoples Friendship University of Russia"	Unclassified	IPv4	22

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS12722	RECONN LLC	Hosting	IPv4	2,271
AS5386	Federal State Budgetary Institution of Science "Space Research Institute of the Russian Academy of Sciences".	Unclassified	IPv4	366
AS49834	Best Hosting Company, LLC	Unclassified	IPv4	305
AS49554	P.P.Shirshov Institute of Oceanology RAS	Unclassified	IPv4	114
AS34849	Federal State Institution of Higher Professional Education "Peoples Friendship University of Russia"	Unclassified	IPv4	22

Provenance

Where this comes from

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