Observed topology

AS20815 GRN-AS GRN Serveis Telematics SL

Residential RIPE Cable/DSL/ISP

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

Upstream graph Who carries AS20815, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS20815 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20815: 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.

AS	Network	Type	Families	Paths seen
AS210321	Operadors Quilometre Zero S.L.	Unclassified	IPv4	540
AS35699	Adamo Telecom Iberia S.A.	Unclassified	IPv4	36
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	9
AS37721	Virtual Technologies & Solutions	Residential	IPv4	9

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS60551	D.P.S. Giro-consulting S.L.	Unclassified	IPv4	462

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS210321	Operadors Quilometre Zero S.L.	Unclassified	IPv4	953
AS60551	D.P.S. Giro-consulting S.L.	Unclassified	IPv4	462
AS35699	Adamo Telecom Iberia S.A.	Unclassified	IPv4	71
AS8218	Zayo Infrastructure France SA	Unclassified	IPv4	16
AS37721	Virtual Technologies & Solutions	Residential	IPv4	16

Provenance

Where this comes from

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