Observed topology

AS214379 SPN South Park Networks LLC

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 5

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214379: 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
AS50263	A-Systems Sp. z o.o.	Unclassified	IPv4 IPv6	225
AS3399	Obenet AB	Unclassified	IPv4 IPv6	150
AS6204	ZET Communications S.R.L.	Unclassified	IPv4 IPv6	138
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	80
AS396998	Path Network, Inc.	Unclassified	IPv4	59
AS49559	A-Systems Sp. z o.o.	Unclassified	IPv4 IPv6	26

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS205380	GeekTeam L.L.C-FZ	Unclassified	IPv4	62

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS50263	A-Systems Sp. z o.o.	Unclassified	IPv4 IPv6	252
AS6204	ZET Communications S.R.L.	Unclassified	IPv4 IPv6	162
AS3399	Obenet AB	Unclassified	IPv4 IPv6	150
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	90
AS205380	GeekTeam L.L.C-FZ	Unclassified	IPv4	62
AS396998	Path Network, Inc.	Unclassified	IPv4	59
AS49559	A-Systems Sp. z o.o.	Unclassified	IPv4 IPv6	27

Provenance

Where this comes from

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