Adjacent networks
AS206813 AS4830ORG
Unclassified RIPE
Adjacency
Adjacent networks
Every AS seen directly next to AS206813 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9211 | Nawork Internet Informationssysteme GmbH | Hosting | IPv4 IPv6 | 274 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 231 |
| AS47147 | Anexia Cloud Solutions GmbH | Unclassified | IPv4 IPv6 | 60 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 45 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 40 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 33 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 IPv6 | 30 |
| AS49745 | Kai Siering | Unclassified | IPv6 | 24 |
| AS9136 | Wobcom GmbH | Residential | IPv4 IPv6 | 20 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 20 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 16 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 7 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 5 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 5 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 4 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 4 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 4 |
| AS12731 | IPHH Internet Port Hamburg GmbH | Unclassified | IPv6 | 3 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 3 |
| AS37100 | SEACOM Limited | Unclassified | IPv4 | 3 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 2 |
| AS34019 | Hivane Association | Unclassified | IPv4 | 2 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 2 |
| AS213241 | TECHIT.BE SRL | Residential | IPv6 | 2 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 1 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 1 |
| AS58057 | Securebit AG | Unclassified | IPv6 | 1 |
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.
Derived from routing tables collected at 2026-10-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.22M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.