asn.dev

Observed topology

AS215362 PROMO-PLUS

Unclassified RIPE Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215362: 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
AS9002RETN LimitedUnclassifiedIPv4 IPv6185
AS174Cogent Communications, LLCTransitIPv4 IPv664
AS8953Orange Romania S.A.ResidentialIPv4 IPv622

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211281NEOHOST SRLUnclassifiedIPv4 IPv6239
AS205563Marc GomezUnclassifiedIPv674
AS205941Lungu Stefan GabrielUnclassifiedIPv637
AS215261ByteFly KftHostingIPv45
AS207590Matteo Filiberto Sciacca trading as LocLixHostingIPv42
AS218995Bobeica Mihaita DavidUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4 IPv6305
AS211281NEOHOST SRLUnclassifiedIPv4 IPv6239
AS8953Orange Romania S.A.ResidentialIPv4 IPv6229
AS174Cogent Communications, LLCTransitIPv4 IPv695
AS205563Marc GomezUnclassifiedIPv674
AS205941Lungu Stefan GabrielUnclassifiedIPv637
AS215261ByteFly KftHostingIPv45
AS207590Matteo Filiberto Sciacca trading as LocLixHostingIPv42
AS218995Bobeica Mihaita DavidUnclassifiedIPv61

Provenance

Where this comes from

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