Observed topology

AS62532 NJEDge.Net, Inc.

Unclassified ARIN Educational/Research

Upstreams 0 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

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

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS88	Princeton University	Unclassified	IPv4 IPv6	200
AS395139	NewYork-Presbyterian Hospital	Unclassified	IPv4	187
AS40591	Bucknell University	Unclassified	IPv4 IPv6	65
AS32993	The Simons Foundation, Inc.	Unclassified	IPv4 IPv6	43
AS1436	Meridian Health System	Unclassified	IPv4	7
AS4246	New Jersey Institute of Technology	Education	IPv4	5

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS11164	Internet2	Education	IPv4 IPv6	336
AS88	Princeton University	Unclassified	IPv4 IPv6	200
AS395139	NewYork-Presbyterian Hospital	Unclassified	IPv4	187
AS11537	Internet2	Unclassified	IPv4	178
AS40591	Bucknell University	Unclassified	IPv4 IPv6	65
AS32993	The Simons Foundation, Inc.	Unclassified	IPv4 IPv6	43
AS1436	Meridian Health System	Unclassified	IPv4	14
AS4246	New Jersey Institute of Technology	Education	IPv4	5

Provenance

Where this comes from

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