asn.dev

Observed topology

AS200461 V6NODE-AS Ian David Klemm

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200461: 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
AS58212dataforest GmbHUnclassifiedIPv4 IPv6363
AS400304Redoubt NetworksHostingIPv4 IPv691

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44103The Mastermind Holding B.V.UnclassifiedIPv4 IPv6273
AS205563Marc GomezUnclassifiedIPv666
AS207388Rick Bakker trading as Bakker ITUnclassifiedIPv460
AS212150RTM Networks B.V.UnclassifiedIPv460
AS216395HostBet Cloud Technologies Private LimitedUnclassifiedIPv460
AS206042Suhail HarisUnclassifiedIPv636
AS197614Ian David KlemmUnclassifiedIPv633
AS200394BLS media GmbHUnclassifiedIPv633
AS216052Craig SchulzUnclassifiedIPv633
AS202986Lukas TautzUnclassifiedIPv611

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS58212dataforest GmbHUnclassifiedIPv4 IPv61,138
AS44103The Mastermind Holding B.V.UnclassifiedIPv4 IPv6383
AS400304Redoubt NetworksHostingIPv4 IPv691
AS205563Marc GomezUnclassifiedIPv666
AS207388Rick Bakker trading as Bakker ITUnclassifiedIPv460
AS212150RTM Networks B.V.UnclassifiedIPv460
AS216395HostBet Cloud Technologies Private LimitedUnclassifiedIPv460
AS206042Suhail HarisUnclassifiedIPv636
AS197614Ian David KlemmUnclassifiedIPv633
AS200394BLS media GmbHUnclassifiedIPv633

All 12 adjacent →

Provenance

Where this comes from

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