asn.dev

Observed topology

AS59492 MEGOGO-AS MEGOGO-LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59492: 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
AS3255LLC EKSINTECHUnclassifiedIPv4235
AS9002RETN LimitedUnclassifiedIPv4 IPv686
AS28917Fiord Networks, UABUnclassifiedIPv435
AS44600"GIGATRANS UKRAINE", LLCUnclassifiedIPv421
AS50263A-Systems Sp. z o.o.UnclassifiedIPv419
AS3303Swisscom (Schweiz) AGResidentialIPv46
AS24482SG.GSHostingIPv46
AS8218Zayo Infrastructure France SAUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204453VASKIANI VENTURES LIMITEDHostingIPv422

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3255LLC EKSINTECHUnclassifiedIPv4235
AS9002RETN LimitedUnclassifiedIPv4 IPv690
AS28917Fiord Networks, UABUnclassifiedIPv453
AS204453VASKIANI VENTURES LIMITEDHostingIPv422
AS44600"GIGATRANS UKRAINE", LLCUnclassifiedIPv421
AS50263A-Systems Sp. z o.o.UnclassifiedIPv419
AS3303Swisscom (Schweiz) AGResidentialIPv46
AS24482SG.GSHostingIPv46
AS8218Zayo Infrastructure France SAUnclassifiedIPv41

Provenance

Where this comes from

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