Observed topology

AS56504 HOSTCIRCLE-L-NL HostCircle B.V.

Hosting RIPE Network Services

Upstreams 8 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS56504: 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
AS1299	Arelion Sweden AB	Transit	IPv4	276
AS6939	Hurricane Electric LLC	Transit	IPv4	50
AS1103	SURF B.V.	Unclassified	IPv4	5
AS20764	CJSC RASCOM	Unclassified	IPv4	5
AS24482	SG.GS	Hosting	IPv4	5
AS34019	Hivane Association	Unclassified	IPv4	5
AS34927	iFog GmbH	Hosting	IPv4	5
AS37721	Virtual Technologies & Solutions	Residential	IPv4	5

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS47674	Consultoria Em Tecnologias De Informacao, Sociedade Unipessoal LDA	Unclassified	IPv4	1,025

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4	1,301
AS47674	Consultoria Em Tecnologias De Informacao, Sociedade Unipessoal LDA	Unclassified	IPv4	1,025
AS6939	Hurricane Electric LLC	Transit	IPv4	50
AS1103	SURF B.V.	Unclassified	IPv4	5
AS20764	CJSC RASCOM	Unclassified	IPv4	5
AS24482	SG.GS	Hosting	IPv4	5
AS34019	Hivane Association	Unclassified	IPv4	5
AS34927	iFog GmbH	Hosting	IPv4	5
AS37721	Virtual Technologies & Solutions	Residential	IPv4	5

Provenance

Where this comes from

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