asn.dev

Observed topology

AS3479 PEACHNET-AS3479

Education ARIN Educational/Research

Upstreams 5 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 0
Upstream graph Who carries AS3479, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS3479 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3479: 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
AS174Cogent Communications, LLCTransitIPv4754
AS10490Georgia Institute of TechnologyEducationIPv4337
AS6939Hurricane Electric LLCTransitIPv4205
AS396450Internet2UnclassifiedIPv4118
AS1299Arelion Sweden ABTransitIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS21517Kennesaw State UniversityUnclassifiedIPv4272
AS18759Georgia Southern UniversityUnclassifiedIPv498
AS398060Augusta UniversityUnclassifiedIPv455
AS3480Board of Regents of the University System of GeorgiaEducationIPv415

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv41,036
AS10490Georgia Institute of TechnologyEducationIPv4576
AS21517Kennesaw State UniversityUnclassifiedIPv4272
AS6939Hurricane Electric LLCTransitIPv4244
AS3480Board of Regents of the University System of GeorgiaEducationIPv4135
AS396450Internet2UnclassifiedIPv4118
AS18759Georgia Southern UniversityUnclassifiedIPv498
AS398060Augusta UniversityUnclassifiedIPv455
AS1299Arelion Sweden ABTransitIPv41

Provenance

Where this comes from

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