asn.dev

Observed topology

AS39184 ULTRANET-AS

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39184: 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 ABTransitIPv48,423
AS9002RETN LimitedUnclassifiedIPv42,727
AS3303Swisscom (Schweiz) AGResidentialIPv4199
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4199
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4199

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199702VIM TV LTDUnclassifiedIPv4354
AS198783ET HALIL ADEMUnclassifiedIPv433
AS42293AVALAUnclassifiedIPv422

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv48,695
AS9002RETN LimitedUnclassifiedIPv42,842
AS199702VIM TV LTDUnclassifiedIPv4354
AS3303Swisscom (Schweiz) AGResidentialIPv4206
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4206
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4206
AS198783ET HALIL ADEMUnclassifiedIPv433
AS42293AVALAUnclassifiedIPv422
AS8218Zayo Infrastructure France SAUnclassifiedIPv41

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.