asn.dev

Observed topology

AS200242 de-theirs Ember Ana Reimer

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS200242: 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
AS210152Jon Vanvik trading as Vanvik InternetUnclassifiedIPv6151
AS917Misaka Network, Inc.UnclassifiedIPv4 IPv6122
AS34927iFog GmbHHostingIPv699
AS21738RozintResidentialIPv668
AS142064VergeTelUnclassifiedIPv653
AS6939Hurricane Electric LLCTransitIPv648
AS208453Johan Karlsson trading as SweHostingHostingIPv636
AS59678SYSTEM36 LLCHostingIPv632
AS52025ParadoxNetworks LimitedUnclassifiedIPv69
AS205794JINZE YANGUnclassifiedIPv67

All 17 upstreams →

Transit

Downstream networks

inferred

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

All 17

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

ASNetworkTypeFamiliesPaths seen
AS210152Jon Vanvik trading as Vanvik InternetUnclassifiedIPv6151
AS917Misaka Network, Inc.UnclassifiedIPv4 IPv6122
AS34927iFog GmbHHostingIPv699
AS21738RozintResidentialIPv668
AS142064VergeTelUnclassifiedIPv653
AS6939Hurricane Electric LLCTransitIPv648
AS208453Johan Karlsson trading as SweHostingHostingIPv636
AS59678SYSTEM36 LLCHostingIPv632
AS52025ParadoxNetworks LimitedUnclassifiedIPv69
AS205794JINZE YANGUnclassifiedIPv67

All 17 adjacent →

Provenance

Where this comes from

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