asn.dev

Observed topology

AS32899 BRESCOBROADBAND

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32899: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv61,657
AS174Cogent Communications, LLCTransitIPv4 IPv6191
AS3356Level 3 Parent, LLCTransitIPv4189
AS3257GTT Communications Inc.TransitIPv4 IPv6115
AS20205Amplex Electric, Inc.ResidentialIPv4 IPv634

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS398430Speedwavz LLPUnclassifiedIPv4264
AS62866OHIO IXHostingIPv4 IPv668
AS397883City of HilliardUnclassifiedIPv466
AS394828VALTECH ENTERPRISES, LLCUnclassifiedIPv429
AS25787Rowe Wireless Networks LLCResidentialIPv415
AS47070Vineyard ColumbusUnclassifiedIPv43
AS46330Licking Memorial HospitalUnclassifiedIPv41

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,091
AS174Cogent Communications, LLCTransitIPv4 IPv6329
AS398430Speedwavz LLPUnclassifiedIPv4264
AS3356Level 3 Parent, LLCTransitIPv4222
AS3257GTT Communications Inc.TransitIPv4 IPv6194
AS62866OHIO IXHostingIPv4 IPv668
AS397883City of HilliardUnclassifiedIPv466
AS20205Amplex Electric, Inc.ResidentialIPv4 IPv639
AS394828VALTECH ENTERPRISES, LLCUnclassifiedIPv429
AS25787Rowe Wireless Networks LLCResidentialIPv415

All 14 adjacent →

Provenance

Where this comes from

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