asn.dev

Observed topology

AS200482 nexserv nexserv GmbH

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200482: 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
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6608
AS48314Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KGUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS216081Paulo Gobbato trading as Gobbato IT LoesungenUnclassifiedIPv4 IPv6226
AS213392Tan SiewertUnclassifiedIPv4 IPv652

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6852
AS216081Paulo Gobbato trading as Gobbato IT LoesungenUnclassifiedIPv4 IPv6226
AS213392Tan SiewertUnclassifiedIPv4 IPv652
AS48314Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KGUnclassifiedIPv4 IPv638

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.