asn.dev

Observed topology

AS209642 MEJIRONETWORK

Unclassified RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209642: 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
AS38008Aperture Science LimitedUnclassifiedIPv4 IPv6594
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv460

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS132009True Internet Co., Ltd.UnclassifiedIPv461
AS132407Verisk Nepal Pvt. Ltd.UnclassifiedIPv461
AS136540The Ogilvy Group, LLC.UnclassifiedIPv461
AS140052Behenobe Trade Services Pte. Ltd.UnclassifiedIPv461
AS140676Alphawest Services Pty LtdUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38008Aperture Science LimitedUnclassifiedIPv4 IPv6899
AS132009True Internet Co., Ltd.UnclassifiedIPv461
AS132407Verisk Nepal Pvt. Ltd.UnclassifiedIPv461
AS136540The Ogilvy Group, LLC.UnclassifiedIPv461
AS140052Behenobe Trade Services Pte. Ltd.UnclassifiedIPv461
AS140676Alphawest Services Pty LtdUnclassifiedIPv461
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv460

Provenance

Where this comes from

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