asn.dev

Observed topology

AS62713 AS-PUBMATIC

Hosting ARIN Content

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

Transit

Upstream networks

All 34

Networks observed carrying traffic for AS62713: 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 ABTransitIPv4559
AS3356Level 3 Parent, LLCTransitIPv4330
AS3257GTT Communications Inc.TransitIPv4315
AS6939Hurricane Electric LLCTransitIPv4243
AS2914NTT America, Inc.TransitIPv4 IPv6145
AS4637Telstra GlobalUnclassifiedIPv4 IPv657
AS24482SG.GSHostingIPv428
AS34549meerfarbig GmbH & Co. KGHostingIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv414
AS293ESnetUnclassifiedIPv411

All 34 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 34

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4559
AS3356Level 3 Parent, LLCTransitIPv4330
AS3257GTT Communications Inc.TransitIPv4315
AS6939Hurricane Electric LLCTransitIPv4243
AS2914NTT America, Inc.TransitIPv4 IPv6145
AS4637Telstra GlobalUnclassifiedIPv4 IPv657
AS24482SG.GSHostingIPv428
AS34549meerfarbig GmbH & Co. KGHostingIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv414
AS293ESnetUnclassifiedIPv411

All 34 adjacent →

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.