asn.dev

Observed topology

AS208210 Sarah Rossius trading as Servperso Systems

Unclassified RIPE

Upstreams 3 carry this network
Downstreams 32 this network carries
Adjacent (IPv4) 12
Adjacent (IPv6) 31
Upstream graph Who carries AS208210, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS208210 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208210: 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
AS6939Hurricane Electric LLCTransitIPv69
AS24482SG.GSHostingIPv61
AS58057Securebit AGUnclassifiedIPv61

Transit

Downstream networks

All 32

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

ASNetworkTypeFamiliesPaths seen
AS219511Serge KrierUnclassifiedIPv6163
AS200202Fuze III SARLUnclassifiedIPv619
AS212871SouverIT UGUnclassifiedIPv612
AS218360NovaMX B.V.UnclassifiedIPv4 IPv69
AS43272DOTNET SH.P.KResidentialIPv4 IPv64
AS60735Konstantin VerbaHostingIPv64
AS208549Christian EhrigHostingIPv44
AS218244MasterVM Europe L.L.CUnclassifiedIPv44
AS218606Samuel OechslerUnclassifiedIPv4 IPv64
AS219271Mathias Jellesmark Fiskbaek trading as Beriffa GroupUnclassifiedIPv64

All 32 downstreams →

Adjacency

Adjacent networks

All 38

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6172
AS219511Serge KrierUnclassifiedIPv6163
AS58057Securebit AGUnclassifiedIPv664
AS200202Fuze III SARLUnclassifiedIPv619
AS24482SG.GSHostingIPv612
AS212871SouverIT UGUnclassifiedIPv612
AS6797GlobalConnect ABUnclassifiedIPv411
AS31543myNet GmbHResidentialIPv69
AS218360NovaMX B.V.UnclassifiedIPv4 IPv69
AS43272DOTNET SH.P.KResidentialIPv4 IPv64

All 38 adjacent →

Provenance

Where this comes from

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