Observed topology
AS50300 CUSTDC
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS50300: 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 | 438 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 397 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 321 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 277 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 159 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 155 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 101 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 76 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 45 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 45 |
Transit
Downstream networks
Networks for which AS50300 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 | 4,978 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 4,938 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,369 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 2,162 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,923 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,696 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 1,590 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 1,493 |
| AS5416 | B.S.C. | Unclassified | IPv4 IPv6 | 1,472 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 | 1,294 |
Adjacency
Adjacent networks
Every AS seen directly next to AS50300 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 314,664 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 257,210 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 164,832 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 144,145 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 121,675 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 51,003 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 32,783 |
| AS64049 | Reliance Jio Infocomm Pte Ltd Singapore | Unclassified | IPv4 IPv6 | 10,283 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 IPv6 | 9,978 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 8,530 |
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.