asn.dev

Observed topology

AS6984 NYNEX-AS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6984: 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
AS701Verizon BusinessResidentialIPv4 IPv62,479
AS3356Level 3 Parent, LLCTransitIPv41,134
AS702Verizon BusinessUnclassifiedIPv4 IPv6354
AS703Verizon BusinessUnclassifiedIPv4231
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6155
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6154

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS32091Tracfone WirelessUnclassifiedIPv4180
AS18461Verizon BusinessUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS701Verizon BusinessResidentialIPv4 IPv62,511
AS3356Level 3 Parent, LLCTransitIPv41,342
AS702Verizon BusinessUnclassifiedIPv4 IPv6354
AS703Verizon BusinessUnclassifiedIPv4231
AS32091Tracfone WirelessUnclassifiedIPv4180
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv6155
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6154
AS18461Verizon BusinessUnclassifiedIPv460

Provenance

Where this comes from

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