asn.dev

Observed topology

AS11367 ICENET

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11367: 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
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv6627
AS10396DATACOM CARIBE, INC.ResidentialIPv4 IPv6416
AS62627WorldNet Telecommunications, LLCUnclassifiedIPv472

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS23534Puerto Rico Medical Services AdministrationUnclassifiedIPv4279
AS27021Quest Diagnostics, Inc.UnclassifiedIPv442
AS54123COSVI'S-ASSET MANAGEMENT CORP.UnclassifiedIPv442
AS62627WorldNet Telecommunications, LLCUnclassifiedIPv42
AS22109Universal Group, Inc.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12956TELEFONICA GLOBAL SOLUTIONS SLTransitIPv4 IPv6947
AS10396DATACOM CARIBE, INC.ResidentialIPv4 IPv6462
AS23534Puerto Rico Medical Services AdministrationUnclassifiedIPv4279
AS62627WorldNet Telecommunications, LLCUnclassifiedIPv474
AS27021Quest Diagnostics, Inc.UnclassifiedIPv442
AS54123COSVI'S-ASSET MANAGEMENT CORP.UnclassifiedIPv442
AS22109Universal Group, Inc.UnclassifiedIPv41

Provenance

Where this comes from

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