asn.dev

Observed topology

AS39798 MivoCloud MivoCloud SRL

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39798: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6682
AS63023GTHostHostingIPv4 IPv6362
AS397373H4Y Technologies LLCHostingIPv4 IPv6246
AS174Cogent Communications, LLCTransitIPv4 IPv6153
AS34959KVIKTEL LLCHostingIPv4 IPv696
AS397423Tier.Net Technologies LLCHostingIPv4 IPv695

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209588Flyservers S.A.HostingIPv4 IPv6102
AS42424ICS Endava SRLUnclassifiedIPv471

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6842
AS63023GTHostHostingIPv4 IPv6362
AS397373H4Y Technologies LLCHostingIPv4 IPv6246
AS174Cogent Communications, LLCTransitIPv4 IPv6166
AS209588Flyservers S.A.HostingIPv4 IPv6102
AS34959KVIKTEL LLCHostingIPv4 IPv696
AS397423Tier.Net Technologies LLCHostingIPv4 IPv695
AS42424ICS Endava SRLUnclassifiedIPv471

Provenance

Where this comes from

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