asn.dev

Observed topology

AS215955 ALTEASYSTEMS Fixed Line ISP

Unclassified RIPE

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

Transit

Upstream networks

inferred

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 GmbHUnclassifiedIPv4104
AS2914NTT America, Inc.TransitIPv485
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv429
AS5511Orange S.A.TransitIPv48
AS24482SG.GSHostingIPv44
AS33891Core-Backbone GmbHHostingIPv44
AS48185team.blue NVUnclassifiedIPv44
AS50300CustodianDC LimitedUnclassifiedIPv44
AS174Cogent Communications, LLCTransitIPv42

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
AS203127TELESPAZIO FRANCE SASUnclassifiedIPv461
AS206865COAXIS ASP SASUnclassifiedIPv45

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4130
AS2914NTT America, Inc.TransitIPv4111
AS203127TELESPAZIO FRANCE SASUnclassifiedIPv461
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv436
AS5511Orange S.A.TransitIPv410
AS24482SG.GSHostingIPv45
AS33891Core-Backbone GmbHHostingIPv45
AS48185team.blue NVUnclassifiedIPv45
AS50300CustodianDC LimitedUnclassifiedIPv45

All 12 adjacent →

Provenance

Where this comes from

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