asn.dev

Observed topology

AS16342 TOYA Toya sp.z.o.o

Residential RIPE

Upstreams 13 carry this network
Downstreams 18 this network carries
Adjacent (IPv4) 29
Adjacent (IPv6) 6
Upstream graph Who carries AS16342, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS16342 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS16342: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6319
AS9002RETN LimitedUnclassifiedIPv4 IPv6257
AS6939Hurricane Electric LLCTransitIPv625
AS50673Serverius Holding B.V.UnclassifiedIPv420
AS24482SG.GSHostingIPv4 IPv612
AS33891Core-Backbone GmbHHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS56655Gigahost ASUnclassifiedIPv411
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv411
AS8218Zayo Infrastructure France SAUnclassifiedIPv49

All 13 upstreams →

Transit

Downstream networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS30782Toya sp.z.o.oUnclassifiedIPv4182
AS29553Toya sp.z.o.oUnclassifiedIPv4180
AS42084Toya sp.z.o.oUnclassifiedIPv4122
AS43244TELNET Sp. z o.o.UnclassifiedIPv461
AS48633KAN Sp. z o.o.UnclassifiedIPv461
AS51619Toya sp.z.o.oUnclassifiedIPv460
AS50331CITYNET Sp.z o.o.ResidentialIPv456
AS56819Urzad Marszalkowski w LodziUnclassifiedIPv455
AS44535Transfer Multisort Elektronik Sp. z o. o.UnclassifiedIPv431
AS204569REGIONALNA ROZGLOSNIA W LODZI "RADIO LODZ" S.A. W LIKWIDACJIUnclassifiedIPv430

All 18 downstreams →

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6790
AS9002RETN LimitedUnclassifiedIPv4 IPv6535
AS30782Toya sp.z.o.oUnclassifiedIPv4182
AS29553Toya sp.z.o.oUnclassifiedIPv4180
AS42084Toya sp.z.o.oUnclassifiedIPv4122
AS51619Toya sp.z.o.oUnclassifiedIPv4100
AS6939Hurricane Electric LLCTransitIPv4 IPv687
AS43244TELNET Sp. z o.o.UnclassifiedIPv461
AS48633KAN Sp. z o.o.UnclassifiedIPv461
AS50331CITYNET Sp.z o.o.ResidentialIPv456

All 31 adjacent →

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.