Observed topology
AS212508 LOWHOSTING-AS
Unclassified RIPE Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS212508: 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.
Transit
Downstream networks
Networks for which AS212508 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12586 | GHOSTnet GmbH | Hosting | IPv4 | 455 |
| AS208328 | Luigi Labate | Hosting | IPv4 IPv6 | 94 |
| AS13101 | TNG Stadtnetz GmbH | Residential | IPv4 | 33 |
| AS59790 | Marco Bungalski GmbH | Residential | IPv4 | 32 |
| AS35366 | ISPpro Internet KG | Hosting | IPv4 | 18 |
| AS29551 | Aixit GmbH | Hosting | IPv4 | 17 |
| AS6774 | Belgacom International Carrier Services SA | Unclassified | IPv4 | 13 |
| AS25220 | equada network GmbH | Hosting | IPv4 | 10 |
| AS51184 | Fonira Telekom GmbH | Residential | IPv4 | 10 |
| AS61493 | InterBS S.R.L. (BAEHOST) | Hosting | IPv4 | 10 |
Adjacency
Adjacent networks
Every AS seen directly next to AS212508 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44393 | Securebit AG | Unclassified | IPv4 | 1,221 |
| AS60068 | Datacamp Limited | Hosting | IPv4 IPv6 | 829 |
| AS12586 | GHOSTnet GmbH | Hosting | IPv4 | 464 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 363 |
| AS208328 | Luigi Labate | Hosting | IPv4 IPv6 | 94 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 78 |
| AS13101 | TNG Stadtnetz GmbH | Residential | IPv4 | 70 |
| AS29551 | Aixit GmbH | Hosting | IPv4 | 52 |
| AS59790 | Marco Bungalski GmbH | Residential | IPv4 | 35 |
| AS35366 | ISPpro Internet KG | Hosting | IPv4 | 18 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.