asn.dev

Observed topology

AS59655 EXINITY-AS

Hosting RIPE Content

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS59655: 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
AS41095IPTP LTDHostingIPv4277
AS174Cogent Communications, LLCTransitIPv4269
AS6461Zayo BandwidthTransitIPv4132
AS3257GTT Communications Inc.TransitIPv4101
AS200449Qrator Labs CZ s.r.o.UnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv444
AS34549meerfarbig GmbH & Co. KGHostingIPv49
AS140951IPTP NetworksUnclassifiedIPv49
AS1836green.ch AGResidentialIPv43
AS6797GlobalConnect ABUnclassifiedIPv43

All 18 upstreams →

Transit

Downstream networks

inferred

Networks for which AS59655 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 18

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

ASNetworkTypeFamiliesPaths seen
AS41095IPTP LTDHostingIPv4277
AS174Cogent Communications, LLCTransitIPv4269
AS6461Zayo BandwidthTransitIPv4132
AS3257GTT Communications Inc.TransitIPv4101
AS200449Qrator Labs CZ s.r.o.UnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv444
AS34549meerfarbig GmbH & Co. KGHostingIPv49
AS140951IPTP NetworksUnclassifiedIPv49
AS1836green.ch AGResidentialIPv43
AS6797GlobalConnect ABUnclassifiedIPv43

All 18 adjacent →

Provenance

Where this comes from

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