asn.dev

Observed topology

AS12826 CYLLENE-ITS

Residential RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS12826: 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
AS6461Zayo BandwidthTransitIPv4 IPv6459
AS6939Hurricane Electric LLCTransitIPv4 IPv6447
AS5511Orange S.A.TransitIPv493
AS24482SG.GSHostingIPv4 IPv618
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv618
AS37721Virtual Technologies & SolutionsResidentialIPv417
AS12779IT.Gate S.p.A.UnclassifiedIPv411
AS20766Association "Gitoyen"UnclassifiedIPv411
AS34927iFog GmbHHostingIPv411
AS9002RETN LimitedUnclassifiedIPv61

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34993CYLLENE ITS SASHostingIPv4 IPv6558

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6721
AS6461Zayo BandwidthTransitIPv4 IPv6664
AS34993CYLLENE ITS SASHostingIPv4 IPv6558
AS5511Orange S.A.TransitIPv4137
AS24482SG.GSHostingIPv4 IPv627
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv627
AS37721Virtual Technologies & SolutionsResidentialIPv425
AS20766Association "Gitoyen"UnclassifiedIPv418
AS12779IT.Gate S.p.A.UnclassifiedIPv411
AS34927iFog GmbHHostingIPv411

All 12 adjacent →

Provenance

Where this comes from

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