Observed topology

AS33951 FORWEB "FORWEB" S.C. Monika Bodetko, Tomasz Pawlowski

Residential RIPE

Upstreams 4 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33951: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	409
AS9002	RETN Limited	Unclassified	IPv4	40
AS197091	METROPORT Sp. z o.o.	Residential	IPv4	20
AS24748	Atman Sp. z o.o.	Hosting	IPv4	5

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS56544	MARLENA Marek Zieba	Unclassified	IPv4	165
AS43435	INSITE Sp. z o.o.	Unclassified	IPv4	59
AS199091	The Best Media Halina Ostrowska	Unclassified	IPv4	9
AS212570	FIBERDOM Sp. z o.o.	Unclassified	IPv4	6

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	608
AS56544	MARLENA Marek Zieba	Unclassified	IPv4	165
AS9002	RETN Limited	Unclassified	IPv4	80
AS43435	INSITE Sp. z o.o.	Unclassified	IPv4	61
AS197091	METROPORT Sp. z o.o.	Residential	IPv4	24
AS199091	The Best Media Halina Ostrowska	Unclassified	IPv4	9
AS212570	FIBERDOM Sp. z o.o.	Unclassified	IPv4	6
AS24748	Atman Sp. z o.o.	Hosting	IPv4	5
AS50263	A-Systems Sp. z o.o.	Unclassified	IPv4	2

Provenance

Where this comes from

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