asn.dev

Observed topology

AS20545 GRENA-AS Georgian Research and Educational Networking Association (GRENA)

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20545: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,111
AS20965GEANT VerenigingUnclassifiedIPv4103
AS35805JSC "Silknet"UnclassifiedIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29289Georgian Technical UniversityUnclassifiedIPv461
AS47575Ivane Javakhishvili Tbilisi State UniversityUnclassifiedIPv461
AS47810Proservice LLCUnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,230
AS20965GEANT VerenigingUnclassifiedIPv4115
AS29289Georgian Technical UniversityUnclassifiedIPv461
AS47575Ivane Javakhishvili Tbilisi State UniversityUnclassifiedIPv461
AS35805JSC "Silknet"UnclassifiedIPv413
AS47810Proservice LLCUnclassifiedIPv49

Provenance

Where this comes from

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