Observed topology
AS50304 BLIX
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS50304: 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 | 2,531 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,231 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 234 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 161 |
| AS57381 | Daniel Husand | Unclassified | IPv4 IPv6 | 104 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 103 |
| AS1103 | SURF B.V. | Unclassified | IPv4 IPv6 | 89 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 87 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 79 |
| AS61292 | Blix Group AS | Unclassified | IPv4 | 79 |
Transit
Downstream networks
Networks for which AS50304 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 | 5,249 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 5,115 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 2,183 |
| AS4766 | Korea Telecom | Mobile | IPv4 | 2,155 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,707 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 1,321 |
| AS6057 | Administracion Nacional de Telecomunicaciones | Residential | IPv4 | 1,152 |
| AS15169 | Google LLC | Hosting | IPv4 IPv6 | 1,123 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 | 1,123 |
| AS9381 | HKBN Enterprise Solutions HK Limited | Hosting | IPv4 | 1,100 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50304 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,294,821 |
| AS57381 | Daniel Husand | Unclassified | IPv4 IPv6 | 498,207 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 160,857 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 36,816 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 35,054 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 | 23,473 |
| AS64049 | Reliance Jio Infocomm Pte Ltd Singapore | Unclassified | IPv4 | 15,575 |
| AS32787 | Akamai Technologies, Inc. | Hosting | IPv4 IPv6 | 12,885 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 10,145 |
| AS4766 | Korea Telecom | Mobile | IPv4 | 9,592 |
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.