asn.dev

Observed topology

AS213035 AS-SERVERION Des Capital B.V.

Hosting Spamhaus ASN-DROP RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS213035: 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
AS213753InterEdge B.V.UnclassifiedIPv41,342
AS6939Hurricane Electric LLCTransitIPv4 IPv689
AS24482SG.GSHostingIPv4 IPv618
AS57866Fusix Networks B.V.UnclassifiedIPv417
AS37721Virtual Technologies & SolutionsResidentialIPv415
AS49673Truenetwork LLCUnclassifiedIPv415
AS202365Omer GOLGELIUnclassifiedIPv415
AS401753BIXCE IncUnclassifiedIPv414
AS33891Core-Backbone GmbHHostingIPv44
AS20764CJSC RASCOMUnclassifiedIPv42

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208414WEDOS Internet, a.s.HostingIPv636

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS213753InterEdge B.V.UnclassifiedIPv41,342
AS6939Hurricane Electric LLCTransitIPv4 IPv6121
AS208414WEDOS Internet, a.s.HostingIPv636
AS24482SG.GSHostingIPv4 IPv619
AS57866Fusix Networks B.V.UnclassifiedIPv417
AS37721Virtual Technologies & SolutionsResidentialIPv415
AS49673Truenetwork LLCUnclassifiedIPv415
AS202365Omer GOLGELIUnclassifiedIPv415
AS401753BIXCE IncUnclassifiedIPv4 IPv615
AS33891Core-Backbone GmbHHostingIPv44

All 16 adjacent →

Provenance

Where this comes from

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