Observed topology

AS214073 Heart Internet limited

Unclassified RIPE

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 20

Adjacent (IPv6) 12

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS20738	Heart Internet limited	Hosting	IPv4 IPv6	4,395

Adjacency

Adjacent networks

All 23

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

AS	Network	Type	Families	Paths seen
AS20738	Heart Internet limited	Hosting	IPv4 IPv6	4,395
AS61231	Neos Networks Limited	Unclassified	IPv4	3,053
AS4455	IX Reach Ltd	Unclassified	IPv4 IPv6	521
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	297
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4 IPv6	83
AS50304	Blix Solutions AS	Unclassified	IPv4	52
AS43531	BSO Network Solutions SAS	Unclassified	IPv4	49
AS17639	Converge ICT Solutions Inc.	Unclassified	IPv4 IPv6	29
AS24482	SG.GS	Hosting	IPv4 IPv6	29
AS48185	team.blue NV	Unclassified	IPv4 IPv6	29

All 23 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.