Observed topology

AS56373 WAVE-AS

Residential RIPE Cable/DSL/ISP

Upstreams 7 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS56373: 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
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	327
AS6939	Hurricane Electric LLC	Transit	IPv4	195
AS20804	Exatel S.A.	Unclassified	IPv4	120
AS9002	RETN Limited	Unclassified	IPv4	65
AS33891	Core-Backbone GmbH	Hosting	IPv4	44
AS24115	Equinix	Hosting	IPv4	30
AS24482	SG.GS	Hosting	IPv4	22

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS57890	Jacek Repinski trading as POTel	Residential	IPv4	130
AS197680	Epoka Sp.z o.o.	Unclassified	IPv4	60

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	327
AS6939	Hurricane Electric LLC	Transit	IPv4	213
AS9002	RETN Limited	Unclassified	IPv4	186
AS20804	Exatel S.A.	Unclassified	IPv4	157
AS57890	Jacek Repinski trading as POTel	Residential	IPv4	130
AS197680	Epoka Sp.z o.o.	Unclassified	IPv4	60
AS33891	Core-Backbone GmbH	Hosting	IPv4	50
AS24115	Equinix	Hosting	IPv4	36
AS24482	SG.GS	Hosting	IPv4	27
AS201054	Stowarzyszenie e-Poludnie	Unclassified	IPv4	3

Provenance

Where this comes from

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