asn.dev

Observed topology

AS206813 AS4830ORG

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

All 27

Networks observed carrying traffic for AS206813: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6236
AS9211Nawork Internet Informationssysteme GmbHHostingIPv4 IPv6192
AS47147Anexia Cloud Solutions GmbHUnclassifiedIPv4 IPv679
AS3320Deutsche Telekom AGMobileIPv4 IPv645
AS9002RETN LimitedUnclassifiedIPv4 IPv635
AS50629LWLcom GmbHUnclassifiedIPv4 IPv633
AS5405Inter.link GmbHUnclassifiedIPv4 IPv627
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv624
AS12731IPHH Internet Port Hamburg GmbHUnclassifiedIPv4 IPv620
AS9136Wobcom GmbHResidentialIPv4 IPv616

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49745Kai SieringUnclassifiedIPv636

Adjacency

Adjacent networks

All 30

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6262
AS9211Nawork Internet Informationssysteme GmbHHostingIPv4 IPv6195
AS47147Anexia Cloud Solutions GmbHUnclassifiedIPv4 IPv679
AS3320Deutsche Telekom AGMobileIPv4 IPv646
AS9002RETN LimitedUnclassifiedIPv4 IPv644
AS49745Kai SieringUnclassifiedIPv636
AS50629LWLcom GmbHUnclassifiedIPv4 IPv636
AS5405Inter.link GmbHUnclassifiedIPv4 IPv627
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv625
AS12731IPHH Internet Port Hamburg GmbHUnclassifiedIPv4 IPv620

Provenance

Where this comes from

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