asn.dev

Observed topology

AS25509 VORTEX-AS Skulagotu 19

Residential RIPE Cable/DSL/ISP

Upstreams 22 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 23
Adjacent (IPv6) 1
Upstream graph Who carries AS25509, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS25509 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS25509: 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.

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv660
AS6939Hurricane Electric LLCTransitIPv48
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS50304Blix Solutions ASUnclassifiedIPv42
AS1836green.ch AGResidentialIPv41
AS3741Dimension DataUnclassifiedIPv41
AS4657StarHub LtdResidentialIPv41
AS8551Bezeq International Ltd.UnclassifiedIPv41
AS12552GlobalConnect ABUnclassifiedIPv41
AS12779IT.Gate S.p.A.UnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34678Eignafelag Tolvunar ehfUnclassifiedIPv459

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv688
AS34678Eignafelag Tolvunar ehfUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv416
AS34549meerfarbig GmbH & Co. KGHostingIPv46
AS50304Blix Solutions ASUnclassifiedIPv44
AS1836green.ch AGResidentialIPv42
AS3741Dimension DataUnclassifiedIPv42
AS4657StarHub LtdResidentialIPv42
AS8551Bezeq International Ltd.UnclassifiedIPv42
AS12552GlobalConnect ABUnclassifiedIPv42

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.