Observed topology
AS36530 FUTURE-LAIN
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS36530: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 413 |
| AS17433 | Hytron Network Services Limited | Residential | IPv4 IPv6 | 369 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 79 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 50 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 40 |
| AS210000 | TwentyWAN MB | Hosting | IPv6 | 37 |
| AS35280 | F5 Networks SARL | Hosting | IPv6 | 20 |
| AS15412 | Flag Telecom UK Limited | Unclassified | IPv6 | 12 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 11 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 11 |
Transit
Downstream networks
Networks for which AS36530 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS212259 | Astrix Co., Ltd. | Unclassified | IPv4 IPv6 | 1,213 |
| AS402628 | IDC | Unclassified | IPv4 IPv6 | 1,096 |
| AS401776 | IDC Cube | Unclassified | IPv4 IPv6 | 593 |
| AS134677 | Dromatics Systems Pte Ltd | Unclassified | IPv4 IPv6 | 320 |
| AS398340 | IDC | Unclassified | IPv4 IPv6 | 276 |
| AS215415 | YUWAN NETWORKS LIMITED | Unclassified | IPv4 IPv6 | 186 |
| AS215023 | LIMEE NETWORK LTD | Unclassified | IPv4 | 136 |
| AS151331 | Sora You | Unclassified | IPv6 | 111 |
| AS199436 | BangLong Yang | Unclassified | IPv6 | 108 |
| AS197196 | PANSTAR CLOUD LIMITED | Unclassified | IPv4 IPv6 | 80 |
Adjacency
Adjacent networks
Every AS seen directly next to AS36530 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17433 | Hytron Network Services Limited | Residential | IPv4 IPv6 | 2,533 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,442 |
| AS212259 | Astrix Co., Ltd. | Unclassified | IPv4 IPv6 | 1,213 |
| AS402628 | IDC | Unclassified | IPv4 IPv6 | 1,096 |
| AS210000 | TwentyWAN MB | Hosting | IPv4 IPv6 | 657 |
| AS401776 | IDC Cube | Unclassified | IPv4 IPv6 | 593 |
| AS134677 | Dromatics Systems Pte Ltd | Unclassified | IPv4 IPv6 | 589 |
| AS151331 | Sora You | Unclassified | IPv6 | 513 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 427 |
| AS398340 | IDC | Unclassified | IPv4 IPv6 | 276 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.