Observed topology
AS63473 HOSTHATCH - HostHatch, LLC
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS63473: 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 |
|---|---|---|---|---|
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 1,731 |
| AS212477 | RoyaleHosting BV | Hosting | IPv4 IPv6 | 987 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 781 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 IPv6 | 504 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 445 |
| AS3399 | Obenet AB | Unclassified | IPv4 IPv6 | 283 |
| AS63018 | Dedicated.com | Hosting | IPv4 IPv6 | 276 |
| AS53587 | AZURE TECHNOLOGY CO., LIMITED | Hosting | IPv4 | 199 |
| AS206264 | Amarutu Technology Ltd | Unclassified | IPv4 | 111 |
| AS30058 | FDCservers.net | Unclassified | IPv4 | 77 |
Transit
Downstream networks
Networks for which AS63473 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43969 | Prinode AB | Unclassified | IPv4 | 1,446 |
| AS205563 | Marc Gomez | Unclassified | IPv6 | 675 |
| AS135598 | SIBERFY (PRIVATE) LIMITED | Unclassified | IPv4 | 671 |
| AS209261 | Qiao Jiang | Unclassified | IPv6 | 291 |
| AS139769 | Guangzhou LinSeek Network Technology Co.Ltd | Unclassified | IPv4 | 240 |
| AS32931 | Peaktera | Residential | IPv4 | 177 |
| AS40776 | TaoNet | Hosting | IPv4 IPv6 | 157 |
| AS214344 | Hanxun Xu | Unclassified | IPv4 IPv6 | 154 |
| AS54148 | Dynamic Quantum Networks | Unclassified | IPv4 IPv6 | 147 |
| AS212085 | Alexander Bruegmann | Unclassified | IPv4 IPv6 | 139 |
Adjacency
Adjacent networks
Every AS seen directly next to AS63473 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 4,915 |
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 2,204 |
| AS43969 | Prinode AB | Unclassified | IPv4 | 1,446 |
| AS212477 | RoyaleHosting BV | Hosting | IPv4 IPv6 | 1,083 |
| AS205563 | Marc Gomez | Unclassified | IPv6 | 675 |
| AS135598 | SIBERFY (PRIVATE) LIMITED | Unclassified | IPv4 | 671 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 IPv6 | 666 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 478 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 467 |
| AS63018 | Dedicated.com | Hosting | IPv4 IPv6 | 410 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.