asn.dev

Observed topology

AS14877 FL-14877

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS14877: 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
AS13536FirstLight Fiber, Inc.ResidentialIPv4 IPv6964
AS293ESnetUnclassifiedIPv412

Transit

Downstream networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS14369NmaxUnclassifiedIPv4551
AS53577Ursinus CollegeUnclassifiedIPv4306
AS394962PENNSYLVANIA COLLEGE OF TECHNOLOGYUnclassifiedIPv4140
AS26699Muhlenberg CollegeUnclassifiedIPv493
AS22192Pennsylvania State System of Higher EducationUnclassifiedIPv466
AS394236Luzerne County Community CollegeUnclassifiedIPv464
AS396459County of VenangoUnclassifiedIPv464
AS22198Lafayette CollegeUnclassifiedIPv458
AS36269University of ScrantonUnclassifiedIPv458
AS11395Thiel CollegeEducationIPv457

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS13536FirstLight Fiber, Inc.ResidentialIPv4 IPv62,522
AS14369NmaxUnclassifiedIPv4551
AS53577Ursinus CollegeUnclassifiedIPv4306
AS394962PENNSYLVANIA COLLEGE OF TECHNOLOGYUnclassifiedIPv4140
AS26699Muhlenberg CollegeUnclassifiedIPv493
AS293ESnetUnclassifiedIPv468
AS22192Pennsylvania State System of Higher EducationUnclassifiedIPv466
AS394236Luzerne County Community CollegeUnclassifiedIPv464
AS396459County of VenangoUnclassifiedIPv464
AS22198Lafayette CollegeUnclassifiedIPv458

Provenance

Where this comes from

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