Observed topology
AS30893 NOACKHOSTING-AS
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS30893: 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 |
|---|---|---|---|---|
| AS39889 | Fredrik Holmqvist | Hosting | IPv4 IPv6 | 612 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 207 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 56 |
| AS215551 | KeFF Networks Ltd | Unclassified | IPv4 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 11 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 1 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS30893 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS218964 | QUATTRO APPS LTD | Unclassified | IPv4 | 235 |
| AS13214 | Hans Fredrik Lennart Neij | Hosting | IPv4 IPv6 | 170 |
| AS199950 | HJELM ENTERPRISES AB | Unclassified | IPv4 IPv6 | 157 |
| AS9423 | ServerKing.io, LLC | Unclassified | IPv4 IPv6 | 76 |
| AS205563 | Marc Gomez | Unclassified | IPv6 | 76 |
| AS202147 | VPSUS LTD | Unclassified | IPv4 | 59 |
| AS200690 | Junxiao Shi | Unclassified | IPv6 | 54 |
| AS57257 | Zorins LLC | Unclassified | IPv6 | 53 |
| AS213593 | Nordic Fighter AB | Unclassified | IPv4 IPv6 | 49 |
| AS204789 | BIZBETA LTD | Unclassified | IPv6 | 44 |
Adjacency
Adjacent networks
Every AS seen directly next to AS30893 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39889 | Fredrik Holmqvist | Hosting | IPv4 IPv6 | 1,365 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 557 |
| AS13214 | Hans Fredrik Lennart Neij | Hosting | IPv4 IPv6 | 305 |
| AS218964 | QUATTRO APPS LTD | Unclassified | IPv4 | 235 |
| AS199950 | HJELM ENTERPRISES AB | Unclassified | IPv4 IPv6 | 157 |
| AS9423 | ServerKing.io, LLC | Unclassified | IPv4 IPv6 | 76 |
| AS205563 | Marc Gomez | Unclassified | IPv6 | 76 |
| AS20473 | The Constant Company, LLC | Hosting | IPv4 IPv6 | 75 |
| AS202147 | VPSUS LTD | Unclassified | IPv4 | 59 |
| AS200690 | Junxiao Shi | Unclassified | IPv6 | 54 |
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.