Observed topology

AS401233 ALLIANCE-BROADBAND - Alliance Broadband

Unclassified ARIN

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

Upstream graph Who carries AS401233, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS401233 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS401233: 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.

AS	Network	Type	Families	Paths seen
AS19151	BroadbandONE, LLC	Hosting	IPv4	58
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4	32
AS6939	Hurricane Electric LLC	Transit	IPv4	20
AS49915	Megaport (UK) Limited	Unclassified	IPv4	6
AS24482	SG.GS	Hosting	IPv4	2

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS400414	ROAMR Communications Inc.	Unclassified	IPv4	178

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS400414	ROAMR Communications Inc.	Unclassified	IPv4	178
AS19151	BroadbandONE, LLC	Hosting	IPv4	108
AS46887	Crown Castle Fiber LLC	Unclassified	IPv4	90
AS6939	Hurricane Electric LLC	Transit	IPv4	48
AS49915	Megaport (UK) Limited	Unclassified	IPv4	39
AS3303	Swisscom (Schweiz) AG	Residential	IPv4	6
AS24482	SG.GS	Hosting	IPv4	5

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.