Observed topology
AS1836 GREEN green.ch AG Autonomous System
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS1836: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,072 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 878 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 565 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 461 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 311 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 238 |
| AS12859 | BIT BV | Hosting | IPv4 IPv6 | 81 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 81 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 81 |
| AS37721 | Virtual-Technologies-Solutions-SA | Residential | IPv4 IPv6 | 81 |
Transit
Downstream networks
Networks for which AS1836 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 5,473 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 4,915 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 IPv6 | 3,541 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 2,304 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,674 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 1,469 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 1,324 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 IPv6 | 1,276 |
| AS15169 | Google LLC | Hosting | IPv4 IPv6 | 1,114 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 966 |
Adjacency
Adjacent networks
Every AS seen directly next to AS1836 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS58057 | Securebit AG | Unclassified | IPv4 IPv6 | 652,650 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 208,239 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 84,958 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 71,643 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 34,089 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 IPv6 | 27,417 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 25,532 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 24,082 |
| AS7195 | S.A.S | Unclassified | IPv4 IPv6 | 10,566 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 8,640 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.