asn.dev

Observed topology

AS209533 BGPTUNNEL BGPTunnel.com by iFog GmbH

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS209533: 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
AS34927iFog GmbHHostingIPv638
AS37989DCS1 Pte. Ltd.HostingIPv61
AS58057Securebit AGUnclassifiedIPv61

Transit

Downstream networks

All 107

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

ASNetworkTypeFamiliesPaths seen
AS213367IGOR BISSOLI ZULCAOUnclassifiedIPv4 IPv6128
AS204406Rudolf MaduroUnclassifiedIPv6111
AS205563Marc GomezUnclassifiedIPv6107
AS219013Santiago Fernandez FernandezUnclassifiedIPv696
AS8173Starboard Networks LLCUnclassifiedIPv4 IPv693
AS211411Wylie FowlerUnclassifiedIPv681
AS216339Mald Entertainment Studio, s.r.o.UnclassifiedIPv681
AS216452Edvin Basil SamuvalUnclassifiedIPv676
AS201345Shuma WatanabeUnclassifiedIPv675
AS210199Heiko SchabertUnclassifiedIPv674

Adjacency

Adjacent networks

All 115

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4 IPv61,654
AS6939Hurricane Electric LLCTransitIPv4 IPv6974
AS213367IGOR BISSOLI ZULCAOUnclassifiedIPv4 IPv6128
AS204406Rudolf MaduroUnclassifiedIPv6111
AS205563Marc GomezUnclassifiedIPv6107
AS219013Santiago Fernandez FernandezUnclassifiedIPv696
AS8173Starboard Networks LLCUnclassifiedIPv4 IPv693
AS211411Wylie FowlerUnclassifiedIPv681
AS216339Mald Entertainment Studio, s.r.o.UnclassifiedIPv681
AS216452Edvin Basil SamuvalUnclassifiedIPv676

Provenance

Where this comes from

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