Observed topology
AS209898 ungleich-ungleich-upstream ungleich glarus ag
Unclassified RIPE Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS209898: 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 |
|---|---|---|---|---|
| AS34872 | Sarah Rossius trading as Servperso Systems | Hosting | IPv6 | 34 |
| AS401753 | BIXCE Inc | Unclassified | IPv6 | 2 |
| AS35708 | 4b42 UG | Unclassified | IPv6 | 1 |
| AS56662 | Marcin Gondek | Unclassified | IPv6 | 1 |
| AS56755 | Securebit AG | Unclassified | IPv6 | 1 |
| AS58057 | Securebit AG | Unclassified | IPv6 | 1 |
| AS58299 | Openfactory GmbH | Residential | IPv4 | 1 |
| AS199854 | Jens Thies | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS209898 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS209898 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34872 | Sarah Rossius trading as Servperso Systems | Hosting | IPv4 IPv6 | 1,287 |
| AS213081 | ungleich glarus ag | Unclassified | IPv4 IPv6 | 1,024 |
| AS199553 | ungleich glarus ag | Unclassified | IPv4 IPv6 | 400 |
| AS211894 | ungleich GmbH | Unclassified | IPv4 IPv6 | 131 |
| AS58057 | Securebit AG | Unclassified | IPv4 IPv6 | 47 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 47 |
| AS56662 | Marcin Gondek | Unclassified | IPv6 | 40 |
| AS199854 | Jens Thies | Unclassified | IPv6 | 40 |
| AS35708 | 4b42 UG | Unclassified | IPv6 | 34 |
| AS56755 | Securebit AG | Unclassified | IPv6 | 34 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.46M 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.