asn.dev

Observed topology

AS59659 SECURUS Securus Communications Ltd.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS59659: 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
AS1299Arelion Sweden ABTransitIPv4 IPv683
AS6939Hurricane Electric LLCTransitIPv4 IPv655
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS51048WIFINITY LIMITEDUnclassifiedIPv410
AS33891Core-Backbone GmbHHostingIPv46
AS50304Blix Solutions ASUnclassifiedIPv46
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS48185team.blue NVUnclassifiedIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48954AIMES Management Services LtdUnclassifiedIPv4708
AS205106Pea Soup Hosting LimitedUnclassifiedIPv4116

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS48954AIMES Management Services LtdUnclassifiedIPv4708
AS1299Arelion Sweden ABTransitIPv4 IPv6251
AS6939Hurricane Electric LLCTransitIPv4 IPv6217
AS205106Pea Soup Hosting LimitedUnclassifiedIPv4116
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv688
AS51048WIFINITY LIMITEDUnclassifiedIPv460
AS50304Blix Solutions ASUnclassifiedIPv458
AS33891Core-Backbone GmbHHostingIPv434
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv630
AS24482SG.GSHostingIPv4 IPv630

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.