asn.dev

Observed topology

AS33387 NOCIX

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33387: 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
AS32097WholeSale Internet, Inc.HostingIPv4 IPv61,471

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215595SparkTech LTDUnclassifiedIPv4280
AS55079Third Gear NetworksUnclassifiedIPv4 IPv690
AS45887GPLHost LLCUnclassifiedIPv457
AS40812XTC Limited CompanyUnclassifiedIPv456
AS32030VoIPster Communications, INC.UnclassifiedIPv442
AS197569BASED ON WHAT LLCUnclassifiedIPv424
AS401538Nova86HostingIPv416
AS44324MoeDove LLCResidentialIPv610
AS50763Robert McKayUnclassifiedIPv410
AS65037unnamedUnclassifiedIPv41

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS32097WholeSale Internet, Inc.HostingIPv4 IPv62,180
AS215595SparkTech LTDUnclassifiedIPv4280
AS55079Third Gear NetworksUnclassifiedIPv4 IPv690
AS55207June SlaterUnclassifiedIPv485
AS45887GPLHost LLCUnclassifiedIPv457
AS40812XTC Limited CompanyUnclassifiedIPv456
AS44324MoeDove LLCResidentialIPv648
AS32030VoIPster Communications, INC.UnclassifiedIPv442
AS197569BASED ON WHAT LLCUnclassifiedIPv424
AS401538Nova86HostingIPv416

All 12 adjacent →

Provenance

Where this comes from

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