asn.dev

Observed topology

AS214481 wczapkowicz-as Wojciech Czapkowicz

Hosting RIPE Content

Upstreams 3 carry this network
Downstreams 10 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 7
Upstream graph Who carries AS214481, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS214481 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214481: 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
AS50917Diederik Focko de ZeeUnclassifiedIPv4 IPv6588
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv698
AS219121CLOUFINITY Sp. z o.o.UnclassifiedIPv462

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213905ISPLABS LIMITEDUnclassifiedIPv4 IPv6270
AS205563Marc GomezUnclassifiedIPv672
AS203534Erik OmarovHostingIPv461
AS399266Z Plus LLCUnclassifiedIPv453
AS16909imputUnclassifiedIPv4 IPv651
AS213471YAMAMOTO HiroshiUnclassifiedIPv636
AS213515Honeybank Studios LTDUnclassifiedIPv423
AS214566Centerfield LtdHostingIPv414
AS203868Rifqi Arief PamungkasUnclassifiedIPv64
AS219121CLOUFINITY Sp. z o.o.UnclassifiedIPv41

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS50917Diederik Focko de ZeeUnclassifiedIPv4 IPv61,177
AS213905ISPLABS LIMITEDUnclassifiedIPv4 IPv6271
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv698
AS205563Marc GomezUnclassifiedIPv672
AS219121CLOUFINITY Sp. z o.o.UnclassifiedIPv463
AS203534Erik OmarovHostingIPv461
AS16909imputUnclassifiedIPv4 IPv654
AS399266Z Plus LLCUnclassifiedIPv453
AS213471YAMAMOTO HiroshiUnclassifiedIPv636
AS213515Honeybank Studios LTDUnclassifiedIPv423

All 12 adjacent →

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.