Observed topology
AS62563 AS-GLOBALTELEHOST
Hosting ARIN Content
Transit
Upstream networks
Networks observed carrying traffic for AS62563: 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 |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 801 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 677 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 554 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 168 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 42 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 21 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 21 |
| AS1403 | EBOX | Residential | IPv6 | 2 |
| AS20473 | The Constant Company, LLC | Hosting | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS62563 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS136258 | BrainStorm Network, Inc | Unclassified | IPv4 IPv6 | 302 |
| AS26383 | Baxet Group Inc. | Unclassified | IPv4 IPv6 | 265 |
| AS215540 | GLOBAL CONNECTIVITY SOLUTIONS LLP | Hosting | IPv4 IPv6 | 229 |
| AS30088 | GTHost | Unclassified | IPv4 | 224 |
| AS400992 | ZhouyiSat Communications | Unclassified | IPv4 | 171 |
| AS212552 | BitCommand LLC | Unclassified | IPv4 IPv6 | 147 |
| AS206300 | YUNYOO LTD | Unclassified | IPv4 | 58 |
| AS215925 | VPSVAULT.HOST LTD | Hosting | IPv4 | 58 |
| AS214238 | HOST TELECOM LTD | Unclassified | IPv4 | 57 |
| AS218964 | QUATTRO APPS LTD | Unclassified | IPv4 | 57 |
Adjacency
Adjacent networks
Every AS seen directly next to AS62563 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,315 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,102 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 919 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 340 |
| AS136258 | BrainStorm Network, Inc | Unclassified | IPv4 IPv6 | 302 |
| AS26383 | Baxet Group Inc. | Unclassified | IPv4 IPv6 | 265 |
| AS215540 | GLOBAL CONNECTIVITY SOLUTIONS LLP | Hosting | IPv4 IPv6 | 229 |
| AS30088 | GTHost | Unclassified | IPv4 | 224 |
| AS400992 | ZhouyiSat Communications | Unclassified | IPv4 | 171 |
| AS212552 | BitCommand LLC | Unclassified | IPv4 IPv6 | 147 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-27 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.06M 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.