asn.dev

Observed topology

AS16391 CELITO-1 - Celito Communications, LLC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS16391: 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 IPv6263
AS62CyrusOne LLCUnclassifiedIPv4 IPv6166
AS2711Spirit CommunicationsUnclassifiedIPv491

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS32482Bandwidth Inc.UnclassifiedIPv4 IPv6144
AS401807Intuity Consultants, Inc.UnclassifiedIPv4122
AS53546Legion, Inc.UnclassifiedIPv461
AS10780Pure Storage, INC.UnclassifiedIPv426
AS6250NeoNova Network Services, LLCUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6589
AS62CyrusOne LLCUnclassifiedIPv4 IPv6207
AS32482Bandwidth Inc.UnclassifiedIPv4 IPv6144
AS401807Intuity Consultants, Inc.UnclassifiedIPv4122
AS2711Spirit CommunicationsUnclassifiedIPv4120
AS53546Legion, Inc.UnclassifiedIPv461
AS10780Pure Storage, INC.UnclassifiedIPv426
AS6250NeoNova Network Services, LLCUnclassifiedIPv41

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.