asn.dev

Observed topology

AS39033 MEDIAOPERATOR-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39033: 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
AS31500Global Network Management IncUnclassifiedIPv458
AS42668Nevalink, LLCResidentialIPv426
AS6939Hurricane Electric LLCTransitIPv419
AS28917Fiord Networks, UABUnclassifiedIPv47
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42
AS56655Gigahost ASUnclassifiedIPv42
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv41

Transit

Downstream networks

inferred

Networks for which AS39033 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS31500Global Network Management IncUnclassifiedIPv458
AS42668Nevalink, LLCResidentialIPv426
AS6939Hurricane Electric LLCTransitIPv419
AS28917Fiord Networks, UABUnclassifiedIPv47
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS49673Truenetwork LLCUnclassifiedIPv42
AS56655Gigahost ASUnclassifiedIPv42
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv41

Provenance

Where this comes from

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