Observed topology
AS33185 HIVE-DATA-CENTER - Hive Data Center Inc.
Hosting ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS33185: 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 | 373 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 369 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 184 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 101 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 48 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 40 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 23 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 23 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 16 |
Transit
Downstream networks
Networks for which AS33185 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS398292 | Babish Telecom | Unclassified | IPv4 | 337 |
| AS398041 | XCD Telecom | Unclassified | IPv4 IPv6 | 262 |
| AS398982 | Securitech Systems Inc. | Unclassified | IPv4 | 171 |
| AS205122 | Planisware SA | Hosting | IPv4 IPv6 | 96 |
| AS19168 | XSOLI INC. | Unclassified | IPv4 IPv6 | 93 |
| AS396142 | Alkeron Inc. | Unclassified | IPv4 IPv6 | 93 |
| AS204769 | DigiRDP, LLC | Unclassified | IPv4 IPv6 | 92 |
| AS400426 | SKYTECH COMMUNICATIONS INC. | Unclassified | IPv4 | 85 |
| AS54975 | Inkbridge | Unclassified | IPv4 IPv6 | 68 |
| AS400696 | MIBURA, INC. | Unclassified | IPv4 | 65 |
Adjacency
Adjacent networks
Every AS seen directly next to AS33185 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,132 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 835 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 496 |
| AS398041 | XCD Telecom | Unclassified | IPv4 IPv6 | 362 |
| AS398292 | Babish Telecom | Unclassified | IPv4 | 337 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 312 |
| AS398982 | Securitech Systems Inc. | Unclassified | IPv4 | 171 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 136 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 111 |
| AS205122 | Planisware SA | Hosting | IPv4 IPv6 | 96 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.