Observed topology
AS48014 AlbHost Albanian Hosting SH.P.K.
Hosting RIPE Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS48014: 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 |
|---|---|---|---|---|
| AS49581 | Ferdinand Zink trading as Tube-Hosting | Hosting | IPv4 IPv6 | 524 |
| AS201814 | MEVSPACE sp. z o.o. | Hosting | IPv4 IPv6 | 269 |
| AS213683 | Host.AL Shpk | Hosting | IPv4 IPv6 | 152 |
| AS197071 | active 1 GmbH | Unclassified | IPv4 IPv6 | 100 |
| AS213250 | Dominic Scholz trading as ITP-Solutions GmbH & Co. KG | Unclassified | IPv4 IPv6 | 96 |
| AS58212 | dataforest GmbH | Unclassified | IPv4 IPv6 | 90 |
Transit
Downstream networks
Networks for which AS48014 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS215540 | GLOBAL CONNECTIVITY SOLUTIONS LLP | Hosting | IPv4 IPv6 | 7,494 |
| AS209207 | Digital Hosting Provider LLC | Unclassified | IPv4 IPv6 | 946 |
| AS219359 | Edge Core FZE | Unclassified | IPv4 IPv6 | 511 |
| AS31130 | Albanian Hosting SH.P.K. | Unclassified | IPv4 IPv6 | 389 |
| AS209132 | Alviva Holding Limited | Unclassified | IPv4 | 125 |
| AS209272 | Alviva Holding Limited | Unclassified | IPv4 | 125 |
| AS215707 | Thimaq Strati trading as iHost.al | Unclassified | IPv4 IPv6 | 102 |
Adjacency
Adjacent networks
Every AS seen directly next to AS48014 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS215540 | GLOBAL CONNECTIVITY SOLUTIONS LLP | Hosting | IPv4 IPv6 | 7,549 |
| AS49581 | Ferdinand Zink trading as Tube-Hosting | Hosting | IPv4 IPv6 | 2,965 |
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 2,300 |
| AS201814 | MEVSPACE sp. z o.o. | Hosting | IPv4 IPv6 | 2,089 |
| AS58212 | dataforest GmbH | Unclassified | IPv4 IPv6 | 1,833 |
| AS209207 | Digital Hosting Provider LLC | Unclassified | IPv4 IPv6 | 946 |
| AS197071 | active 1 GmbH | Unclassified | IPv4 IPv6 | 589 |
| AS213683 | Host.AL Shpk | Hosting | IPv4 IPv6 | 527 |
| AS219359 | Edge Core FZE | Unclassified | IPv4 IPv6 | 511 |
| AS61272 | UAB Bacloud | Unclassified | IPv4 IPv6 | 488 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.