Observed topology
AS34872 SERVPERSO_SYSTEMS
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS34872: 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 | 212 |
| AS35133 | Eranium B.V. | Hosting | IPv4 IPv6 | 195 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 183 |
| AS24961 | WIIT AG | Hosting | IPv4 IPv6 | 79 |
| AS60144 | 3W Infra B.V. | Unclassified | IPv4 IPv6 | 54 |
| AS3214 | xTom GmbH | Hosting | IPv4 IPv6 | 49 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 26 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 19 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 19 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv4 IPv6 | 13 |
Transit
Downstream networks
Networks for which AS34872 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 938 |
| AS203226 | Dirk Walde trading as Walde IT-Systeme | Unclassified | IPv4 IPv6 | 301 |
| AS219511 | Serge Krier | Unclassified | IPv6 | 296 |
| AS214865 | Falco Nordmann | Unclassified | IPv4 IPv6 | 273 |
| AS208674 | Association TekitUp | Unclassified | IPv4 IPv6 | 245 |
| AS208549 | Christian Ehrig | Hosting | IPv4 IPv6 | 225 |
| AS8489 | Martin Mersberger EDV Beratung | Unclassified | IPv4 IPv6 | 220 |
| AS212871 | SouverIT UG | Unclassified | IPv6 | 203 |
| AS60391 | Papa-Razzi Media Group A.s.b.l. | Unclassified | IPv6 | 196 |
| AS207099 | Rickard Andrinsson | Unclassified | IPv6 | 182 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34872 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,289 |
| AS60144 | 3W Infra B.V. | Unclassified | IPv4 IPv6 | 3,161 |
| AS24961 | WIIT AG | Hosting | IPv4 IPv6 | 3,126 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 1,743 |
| AS209898 | ungleich glarus ag | Unclassified | IPv4 IPv6 | 1,628 |
| AS3214 | xTom GmbH | Hosting | IPv4 IPv6 | 1,284 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 IPv6 | 747 |
| AS35133 | Eranium B.V. | Hosting | IPv4 IPv6 | 579 |
| AS58057 | Securebit AG | Unclassified | IPv4 IPv6 | 382 |
| AS60391 | Papa-Razzi Media Group A.s.b.l. | Unclassified | IPv4 IPv6 | 347 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.