Observed topology

AS198020 DATACRUNCH Verda Cloud Oy

Hosting RIPE

Upstreams 21 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 21

Adjacent (IPv6) 0

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS198020: 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
AS13335	Cloudflare, Inc.	Hosting	IPv4	432
AS6461	Zayo Bandwidth	Transit	IPv4	85
AS12552	GlobalConnect AB	Unclassified	IPv4	77
AS9002	RETN Limited	Unclassified	IPv4	49
AS1299	Arelion Sweden AB	Transit	IPv4	33
AS24482	SG.GS	Hosting	IPv4	7
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	6
AS3333	Reseaux IP Europeens Network Coordination Centre (RIPE NCC)	Unclassified	IPv4	6
AS48185	team.blue NV	Unclassified	IPv4	6
AS48362	Stadtwerke Feldkirch	Residential	IPv4	6

All 21 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 21

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

AS	Network	Type	Families	Paths seen
AS13335	Cloudflare, Inc.	Hosting	IPv4	432
AS6461	Zayo Bandwidth	Transit	IPv4	85
AS12552	GlobalConnect AB	Unclassified	IPv4	77
AS9002	RETN Limited	Unclassified	IPv4	49
AS1299	Arelion Sweden AB	Transit	IPv4	33
AS24482	SG.GS	Hosting	IPv4	7
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	6
AS3333	Reseaux IP Europeens Network Coordination Centre (RIPE NCC)	Unclassified	IPv4	6
AS48185	team.blue NV	Unclassified	IPv4	6
AS48362	Stadtwerke Feldkirch	Residential	IPv4	6

All 21 adjacent →

Provenance

Where this comes from

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