asn.dev

Observed topology

AS215955 ALTEASYSTEMS-AS ALTEASYSTEMS OU

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS215955: 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
AS5405Inter.link GmbHUnclassifiedIPv488
AS2914NTT America, Inc.TransitIPv481
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv461
AS6939Hurricane Electric LLCTransitIPv425
AS5511Orange S.A.TransitIPv48
AS50304Blix Solutions ASUnclassifiedIPv48
AS20764CJSC RASCOMUnclassifiedIPv44
AS24482SG.GSHostingIPv44
AS33891Core-Backbone GmbHHostingIPv44
AS34019Hivane AssociationUnclassifiedIPv44

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206865COAXIS ASP SASUnclassifiedIPv4332
AS203127TELESPAZIO FRANCE SASUnclassifiedIPv462

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS206865COAXIS ASP SASUnclassifiedIPv4332
AS5405Inter.link GmbHUnclassifiedIPv4245
AS2914NTT America, Inc.TransitIPv4215
AS6939Hurricane Electric LLCTransitIPv474
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv463
AS203127TELESPAZIO FRANCE SASUnclassifiedIPv462
AS50304Blix Solutions ASUnclassifiedIPv422
AS20764CJSC RASCOMUnclassifiedIPv411
AS24482SG.GSHostingIPv411
AS50300CustodianDC LimitedUnclassifiedIPv411

All 20 adjacent →

Provenance

Where this comes from

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