Observed topology

AS43476 LBGK1-AS3 leniwiec.biz Grzegorz Kulewski

Hosting RIPE

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43476: 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	24
AS3356	Level 3 Parent, LLC	Transit	IPv4	23
AS210104	Timplus sp. z o.o.	Residential	IPv4	7
AS33891	Core-Backbone GmbH	Hosting	IPv4	2
AS24115	Equinix	Hosting	IPv4	1
AS24482	SG.GS	Hosting	IPv4	1

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS16288	Sfires Software & Hardware Dariusz Swiderski	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS16288	Sfires Software & Hardware Dariusz Swiderski	Unclassified	IPv4	58
AS1299	Arelion Sweden AB	Transit	IPv4	49
AS3356	Level 3 Parent, LLC	Transit	IPv4	46
AS210104	Timplus sp. z o.o.	Residential	IPv4	14
AS33891	Core-Backbone GmbH	Hosting	IPv4	4
AS24482	SG.GS	Hosting	IPv4	2
AS24115	Equinix	Hosting	IPv4	1

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.