asn.dev

Observed topology

AS17012 PAYPAL

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17012: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6574
AS1299Arelion Sweden ABTransitIPv4332
AS2914NTT America, Inc.TransitIPv4325
AS3257GTT Communications Inc.TransitIPv4 IPv696
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv438
AS4637Telstra GlobalUnclassifiedIPv430

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS26441HyperWALLET Systems IncUnclassifiedIPv4165
AS30393Bill Me LaterUnclassifiedIPv4121

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6747
AS2914NTT America, Inc.TransitIPv4403
AS1299Arelion Sweden ABTransitIPv4355
AS26441HyperWALLET Systems IncUnclassifiedIPv4165
AS30393Bill Me LaterUnclassifiedIPv4121
AS3257GTT Communications Inc.TransitIPv4 IPv6102
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv443
AS4637Telstra GlobalUnclassifiedIPv431

Provenance

Where this comes from

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