Observed topology

AS197099 MULTINET24PL Multinet24 Sp.zoo

Unclassified RIPE Enterprise

Upstreams 5 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS197099: 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
AS219062	Nera sp z.o.o	Unclassified	IPv4	780
AS9002	RETN Limited	Unclassified	IPv6	54
AS6939	Hurricane Electric LLC	Transit	IPv6	39
AS24482	SG.GS	Hosting	IPv4 IPv6	15
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv6	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS205748	INFORSYS SA	Unclassified	IPv4	13
AS205136	OLIMP LABORATORIES Sp. z o.o.	Unclassified	IPv4	10

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS219062	Nera sp z.o.o	Unclassified	IPv4	780
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	60
AS9002	RETN Limited	Unclassified	IPv6	54
AS24482	SG.GS	Hosting	IPv4 IPv6	17
AS205748	INFORSYS SA	Unclassified	IPv4	13
AS205136	OLIMP LABORATORIES Sp. z o.o.	Unclassified	IPv4	10
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv6	3

Provenance

Where this comes from

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