Observed topology
AS6206 NETROUTING-AS
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS6206: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 963 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 548 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 445 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 300 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 63 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 42 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 36 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 34 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 30 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 23 |
Transit
Downstream networks
Networks for which AS6206 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44259 | Ultahost, Inc. | Unclassified | IPv4 | 708 |
| AS214036 | Ultahost, Inc. | Unclassified | IPv4 IPv6 | 696 |
| AS198077 | Need, L.L.C.-FZ | Unclassified | IPv4 | 587 |
| AS2856 | British Telecommunications Limited | Residential | IPv4 | 543 |
| AS399122 | VPS House Technology Group LLC | Unclassified | IPv4 IPv6 | 476 |
| AS40244 | Turnkey Internet Inc. | Hosting | IPv4 IPv6 | 277 |
| AS6977 | LayerSwitch, Inc | Hosting | IPv4 IPv6 | 271 |
| AS15020 | Bandito Networks, Inc | Unclassified | IPv4 IPv6 | 263 |
| AS215929 | Data Campus Limited | Unclassified | IPv4 IPv6 | 244 |
| AS402273 | Instantly.ai | Unclassified | IPv4 IPv6 | 206 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6206 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 5,322 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 4,525 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,393 |
| AS39521 | TNGNET B.V. | Unclassified | IPv4 | 2,065 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,769 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,287 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 846 |
| AS2856 | British Telecommunications Limited | Residential | IPv4 | 812 |
| AS44259 | Ultahost, Inc. | Unclassified | IPv4 | 708 |
| AS214036 | Ultahost, Inc. | Unclassified | IPv4 IPv6 | 696 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.