asn.dev

Observed topology

AS61098 EXOSCALE

Hosting RIPE Content

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

Transit

Upstream networks

All 25

Networks observed carrying traffic for AS61098: 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 IPv6840
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv6667
AS1299Arelion Sweden ABTransitIPv4 IPv6527
AS8447A1 Telekom Austria AGResidentialIPv4 IPv6470
AS6939Hurricane Electric LLCTransitIPv4 IPv6238
AS8717A1 Bulgaria EADResidentialIPv4 IPv6184
AS15994A1 Hrvatska d.o.o.ResidentialIPv4 IPv6112
AS33891Core-Backbone GmbHHostingIPv4 IPv6112
AS6893Saitis Network, N.DesirResidentialIPv4 IPv6100
AS8903LYNTIA NETWORKS S.A.UnclassifiedIPv4 IPv668

All 25 upstreams →

Transit

Downstream networks

inferred

Networks for which AS61098 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 25

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6840
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv6667
AS1299Arelion Sweden ABTransitIPv4 IPv6527
AS8447A1 Telekom Austria AGResidentialIPv4 IPv6470
AS6939Hurricane Electric LLCTransitIPv4 IPv6238
AS8717A1 Bulgaria EADResidentialIPv4 IPv6184
AS15994A1 Hrvatska d.o.o.ResidentialIPv4 IPv6112
AS33891Core-Backbone GmbHHostingIPv4 IPv6112
AS6893Saitis Network, N.DesirResidentialIPv4 IPv6100
AS8903LYNTIA NETWORKS S.A.UnclassifiedIPv4 IPv668

All 25 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.