Observed topology

AS44914 PETRUS-CH-AS Petrus Spolka z ograniczona odpowiedzialnoscia

Residential RIPE

Upstreams 7 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 6

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44914: 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
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	718
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	231
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	76
AS24482	SG.GS	Hosting	IPv4 IPv6	19
AS33891	Core-Backbone GmbH	Hosting	IPv4	17
AS29632	Netassist International EOOD	Unclassified	IPv6	2
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv6	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS43679	Petrus Spolka z ograniczona odpowiedzialnoscia	Residential	IPv4	59
AS209901	COMEL IT Sp. z o. o.	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	761
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	242
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	80
AS43679	Petrus Spolka z ograniczona odpowiedzialnoscia	Residential	IPv4	59
AS24482	SG.GS	Hosting	IPv4 IPv6	20
AS33891	Core-Backbone GmbH	Hosting	IPv4	18
AS29632	Netassist International EOOD	Unclassified	IPv6	2
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv6	2
AS209901	COMEL IT Sp. z o. o.	Unclassified	IPv4	1

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.