Observed topology

AS32145 OPENCAPE - OpenCape Corporation

Unclassified ARIN

Upstreams 2 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32145: 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
AS2914	NTT America, Inc.	Transit	IPv4	289
AS174	Cogent Communications, LLC	Transit	IPv4	182

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS10271	Meganet Communications	Unclassified	IPv4	353
AS40207	Cape Cod Healthcare Inc.	Unclassified	IPv4	118
AS11499	Woods Hole Oceanographic Institution	Unclassified	IPv4	82
AS400357	Southcoast Health System, Inc.	Unclassified	IPv4	82
AS40194	MBL	Unclassified	IPv4	61
AS393690	Massachusetts Maritime Academy	Unclassified	IPv4	40
AS32278	Getwireless.net	Unclassified	IPv4	1

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	726
AS2914	NTT America, Inc.	Transit	IPv4	458
AS10271	Meganet Communications	Unclassified	IPv4	353
AS40207	Cape Cod Healthcare Inc.	Unclassified	IPv4	118
AS11499	Woods Hole Oceanographic Institution	Unclassified	IPv4	82
AS400357	Southcoast Health System, Inc.	Unclassified	IPv4	82
AS40194	MBL	Unclassified	IPv4	61
AS393690	Massachusetts Maritime Academy	Unclassified	IPv4	40
AS14325	OSHEAN, Inc.	Unclassified	IPv4	24
AS32278	Getwireless.net	Unclassified	IPv4	1

Provenance

Where this comes from

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