asn.dev

Observed topology

AS209898 UNGLEICH-PLACE15

Unclassified RIPE Enterprise

Upstreams 7 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 10
Upstream graph Who carries AS209898, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS209898 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv635
AS213081ungleich glarus agUnclassifiedIPv632
AS357084b42 UGUnclassifiedIPv61
AS56755Securebit AGUnclassifiedIPv61
AS58057Securebit AGUnclassifiedIPv61
AS199854Jens ThiesUnclassifiedIPv61
AS401753BIXCE IncUnclassifiedIPv61

Transit

Downstream networks

inferred

Networks for which AS209898 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS213081ungleich glarus agUnclassifiedIPv4 IPv6760
AS211894ungleich GmbHUnclassifiedIPv4 IPv6485
AS199553ungleich glarus agUnclassifiedIPv6164

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS209898 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv61,556
AS213081ungleich glarus agUnclassifiedIPv4 IPv61,002
AS211894ungleich GmbHUnclassifiedIPv4 IPv6485
AS199553ungleich glarus agUnclassifiedIPv4 IPv6304
AS58057Securebit AGUnclassifiedIPv4 IPv676
AS401753BIXCE IncUnclassifiedIPv4 IPv652
AS199854Jens ThiesUnclassifiedIPv644
AS357084b42 UGUnclassifiedIPv633
AS56755Securebit AGUnclassifiedIPv633
AS34549meerfarbig GmbH & Co. KGHostingIPv65

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-24 16:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.19M 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.