asn.dev

Observed topology

AS210728 CYSO-AS-DE CYSO-AMS

Unclassified RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS210728: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6104
AS6939Hurricane Electric LLCTransitIPv4 IPv630
AS25151Cyso Group B.V.HostingIPv420
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv610
AS1836green.ch AGResidentialIPv4 IPv64
AS24482SG.GSHostingIPv4 IPv64
AS34019Hivane AssociationUnclassifiedIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS212024Marc SchmittUnclassifiedIPv4 IPv64

All 21 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44694Cyso Group B.V.UnclassifiedIPv4 IPv6153

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6186
AS44694Cyso Group B.V.UnclassifiedIPv4 IPv6153
AS6939Hurricane Electric LLCTransitIPv4 IPv655
AS25151Cyso Group B.V.HostingIPv420
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv617
AS1836green.ch AGResidentialIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv67
AS34019Hivane AssociationUnclassifiedIPv4 IPv67
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67

All 22 adjacent →

Provenance

Where this comes from

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