asn.dev

Observed topology

AS200735 AS-MUENET

Unclassified RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS200735: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6666
AS6939Hurricane Electric LLCTransitIPv4 IPv6160
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv646
AS24482SG.GSHostingIPv4 IPv620
AS34019Hivane AssociationUnclassifiedIPv4 IPv620
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv620
AS212024Marc SchmittUnclassifiedIPv4 IPv620
AS29632Netassist International EOODUnclassifiedIPv614
AS6797GlobalConnect ABUnclassifiedIPv413
AS12779IT.Gate S.p.A.UnclassifiedIPv413

Transit

Downstream networks

inferred

Networks for which AS200735 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 15

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv6666
AS6939Hurricane Electric LLCTransitIPv4 IPv6160
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv646
AS24482SG.GSHostingIPv4 IPv620
AS34019Hivane AssociationUnclassifiedIPv4 IPv620
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv620
AS212024Marc SchmittUnclassifiedIPv4 IPv620
AS29632Netassist International EOODUnclassifiedIPv614
AS6797GlobalConnect ABUnclassifiedIPv413
AS12779IT.Gate S.p.A.UnclassifiedIPv413

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.