asn.dev

Observed topology

AS63303 TOUCHTONE-NEWARK

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS63303: 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
AS2914NTT America, Inc.TransitIPv4104
AS701Verizon BusinessResidentialIPv447
AS6939Hurricane Electric LLCTransitIPv428
AS34549meerfarbig GmbH & Co. KGHostingIPv412
AS22652Videotron LteeResidentialIPv48
AS8359MTS PJSCMobileIPv44
AS24482SG.GSHostingIPv44
AS33891Core-Backbone GmbHHostingIPv44
AS37721Virtual Technologies & SolutionsResidentialIPv44
AS9304HGC Global Communications LimitedHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS27479Lake Norman Security Patrol, Inc.UnclassifiedIPv446

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4149
AS701Verizon BusinessResidentialIPv471
AS53828NETWORK INNOVATIONS, LLCUnclassifiedIPv459
AS27479Lake Norman Security Patrol, Inc.UnclassifiedIPv446
AS6939Hurricane Electric LLCTransitIPv444
AS34549meerfarbig GmbH & Co. KGHostingIPv422
AS22652Videotron LteeResidentialIPv414
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS8359MTS PJSCMobileIPv46
AS24482SG.GSHostingIPv46

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 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.