asn.dev

Observed topology

AS8522 FORTH-AS

Education RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8522: 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
AS5408National Infrastructures for Research and Technology S.A.EducationIPv4 IPv6158
AS56910Digital Realty Hellas Single Member S.AUnclassifiedIPv4128

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212984ENISAUnclassifiedIPv463
AS14650Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv4 IPv617
AS197997RegisterBG LtdUnclassifiedIPv4 IPv69
AS20144ICANNUnclassifiedIPv4 IPv65
AS44358Kauno Technologijos UniversitetasUnclassifiedIPv4 IPv62
AS48053Foundation of Research and Technology HellasUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS5408National Infrastructures for Research and Technology S.A.EducationIPv4 IPv6256
AS56910Digital Realty Hellas Single Member S.AUnclassifiedIPv4128
AS212984ENISAUnclassifiedIPv463
AS14650Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv4 IPv617
AS197997RegisterBG LtdUnclassifiedIPv4 IPv69
AS20144ICANNUnclassifiedIPv4 IPv65
AS44358Kauno Technologijos UniversitetasUnclassifiedIPv4 IPv62
AS48053Foundation of Research and Technology HellasUnclassifiedIPv42

Provenance

Where this comes from

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