Observed topology
AS56655 GIGAHOST
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS56655: 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 | 1,646 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 917 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 72 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 58 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 52 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 48 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 47 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 47 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 47 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 | 47 |
Transit
Downstream networks
Networks for which AS56655 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 4,845 |
| AS4837 | CHINA UNICOM China169 Backbone | Mobile | IPv4 IPv6 | 2,115 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,695 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 1,318 |
| AS8866 | Vivacom Bulgaria EAD | Residential | IPv4 | 989 |
| AS12735 | TurkNet Iletisim Hizmetleri A.S. | Unclassified | IPv4 IPv6 | 707 |
| AS216071 | SERVERS TECH FZCO | Hosting | IPv4 | 610 |
| AS9605 | NTT DOCOMO, INC. | Mobile | IPv4 | 516 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 IPv6 | 504 |
| AS216091 | eth0 AS | Hosting | IPv4 IPv6 | 389 |
Adjacency
Adjacent networks
Every AS seen directly next to AS56655 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 800,962 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 369,888 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 361,320 |
| AS4837 | CHINA UNICOM China169 Backbone | Mobile | IPv4 IPv6 | 16,121 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 4,858 |
| AS29049 | Delta Telecom Ltd | Residential | IPv4 | 4,574 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 2,209 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 1,949 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,737 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 1,485 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 16:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.19M 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.