asn.dev

Observed topology

AS33132 CROWNCASTLE-AS33132 - Crown Castle Fiber LLC

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33132: 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
AS46887Crown Castle Fiber LLCUnclassifiedIPv4 IPv63,630

Transit

Downstream networks

All 93

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

ASNetworkTypeFamiliesPaths seen
AS32083Omnispring, LLCHostingIPv41,210
AS21973XponetUnclassifiedIPv4 IPv6826
AS16557Colo SolutionsHostingIPv4 IPv6500
AS32034SPEEDCAST LATAM INC.UnclassifiedIPv4315
AS11809Embry-Riddle UniversityEducationIPv4255
AS10273Florida Power & Light CompanyUnclassifiedIPv4236
AS19982Natural Wireless, LLCUnclassifiedIPv4232
AS400097National Wi-FiUnclassifiedIPv6224
AS13511Univision Communications Inc.UnclassifiedIPv4216
AS12253Leon County Board of County CommisionersUnclassifiedIPv4185

Adjacency

Adjacent networks

All 94

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

ASNetworkTypeFamiliesPaths seen
AS46887Crown Castle Fiber LLCUnclassifiedIPv4 IPv611,865
AS32083Omnispring, LLCHostingIPv41,210
AS21973XponetUnclassifiedIPv4 IPv6826
AS16557Colo SolutionsHostingIPv4 IPv6632
AS32034SPEEDCAST LATAM INC.UnclassifiedIPv4435
AS11809Embry-Riddle UniversityEducationIPv4255
AS10273Florida Power & Light CompanyUnclassifiedIPv4236
AS19982Natural Wireless, LLCUnclassifiedIPv4232
AS400097National Wi-FiUnclassifiedIPv6224
AS13511Univision Communications Inc.UnclassifiedIPv4216

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.