asn.dev

Observed topology

AS216394 WireShield WireShield LTD

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS216394: 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
AS212477RoyaleHosting BVHostingIPv437
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv416
AS4849S3 Company LtdHostingIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44620Netlen Internet Hizmetleri Ltd. Sti.UnclassifiedIPv4226
AS47930BRANDEFENSE BILISIM DANISMANLIK SANAYI VE TICARET ANONIM SIRKETIUnclassifiedIPv460
AS206668Bayram CoskunUnclassifiedIPv449

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS44620Netlen Internet Hizmetleri Ltd. Sti.UnclassifiedIPv4227
AS212477RoyaleHosting BVHostingIPv4202
AS4849S3 Company LtdHostingIPv4107
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv487
AS47930BRANDEFENSE BILISIM DANISMANLIK SANAYI VE TICARET ANONIM SIRKETIUnclassifiedIPv460
AS206668Bayram CoskunUnclassifiedIPv449

Provenance

Where this comes from

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