asn.dev

Observed topology

AS22987 BRIGHTRIDGE

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22987: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6116
AS3257GTT Communications Inc.TransitIPv4 IPv641
AS6939Hurricane Electric LLCTransitIPv4 IPv641
AS24482SG.GSHostingIPv4 IPv64
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv64
AS293ESnetUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14523Greeneville Energy AuthorityUnclassifiedIPv4 IPv6326
AS26111Erwin UtilitiesUnclassifiedIPv4218
AS395562Fireball Wireless LLCUnclassifiedIPv4118
AS46594Business Information Systems, Inc.UnclassifiedIPv433
AS393986Johnson City Power BoardUnclassifiedIPv4 IPv614
AS394286City of Johnson CityUnclassifiedIPv412

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6573
AS14523Greeneville Energy AuthorityUnclassifiedIPv4 IPv6326
AS26111Erwin UtilitiesUnclassifiedIPv4218
AS3257GTT Communications Inc.TransitIPv4 IPv6172
AS6939Hurricane Electric LLCTransitIPv4 IPv6164
AS395562Fireball Wireless LLCUnclassifiedIPv4118
AS46594Business Information Systems, Inc.UnclassifiedIPv433
AS393986Johnson City Power BoardUnclassifiedIPv4 IPv614
AS394286City of Johnson CityUnclassifiedIPv412
AS24482SG.GSHostingIPv4 IPv68

Provenance

Where this comes from

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