asn.dev

Observed topology

AS33951 FORWEB Local internet provider city Lodz in Poland

Residential RIPE

Upstreams 6 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 11
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.

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4185
AS6939Hurricane Electric LLCTransitIPv469
AS3356Level 3 Parent, LLCTransitIPv451
AS197091METROPORT Sp. z o.o.ResidentialIPv445
AS24482SG.GSHostingIPv45
AS24748Atman Sp. z o.o.HostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56544MARLENA Marek ZiebaUnclassifiedIPv490
AS43435INSITE Sp. z o.o.UnclassifiedIPv460
AS199091The Best Media Halina OstrowskaUnclassifiedIPv49
AS212570FIBERDOM Sp. z o.o.UnclassifiedIPv46

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4297
AS6939Hurricane Electric LLCTransitIPv4118
AS56544MARLENA Marek ZiebaUnclassifiedIPv490
AS43435INSITE Sp. z o.o.UnclassifiedIPv462
AS3356Level 3 Parent, LLCTransitIPv451
AS197091METROPORT Sp. z o.o.ResidentialIPv449
AS24482SG.GSHostingIPv49
AS199091The Best Media Halina OstrowskaUnclassifiedIPv49
AS212570FIBERDOM Sp. z o.o.UnclassifiedIPv46
AS50263A-Systems Sp. z o.o.UnclassifiedIPv42

Provenance

Where this comes from

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