asn.dev

Observed topology

AS59675 MYWIRENET-AS

Unclassified RIPE

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS59675: 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
AS88811&1 Versatel GmbHResidentialIPv4 IPv6624
AS1299Arelion Sweden ABTransitIPv4 IPv6123
AS6939Hurricane Electric LLCTransitIPv4 IPv695
AS21473PFALZKOM GmbHUnclassifiedIPv4 IPv683
AS12693e.discom Telekommunikation GmbHUnclassifiedIPv461
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv628
AS1836green.ch AGResidentialIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv610
AS34019Hivane AssociationUnclassifiedIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610

All 23 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS88811&1 Versatel GmbHResidentialIPv4 IPv6624
AS1299Arelion Sweden ABTransitIPv4 IPv6123
AS6939Hurricane Electric LLCTransitIPv4 IPv695
AS21473PFALZKOM GmbHUnclassifiedIPv4 IPv683
AS12693e.discom Telekommunikation GmbHUnclassifiedIPv461
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv628
AS1836green.ch AGResidentialIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv610
AS34019Hivane AssociationUnclassifiedIPv4 IPv610
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610

All 23 adjacent →

Provenance

Where this comes from

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