asn.dev

Observed topology

AS63399 DIALPAD - Dialpad, Inc.

Hosting ARIN

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

Transit

Upstream networks

All 46

Networks observed carrying traffic for AS63399: 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.TransitIPv4 IPv6689
AS1299Arelion Sweden ABTransitIPv4 IPv6329
AS6939Hurricane Electric LLCTransitIPv4 IPv6316
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6258
AS25818CMC NETWORK (PTY) LTDUnclassifiedIPv4 IPv6214
AS3257GTT Communications Inc.TransitIPv4 IPv6153
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6112
AS6461Zayo BandwidthTransitIPv4 IPv698
AS3356Level 3 Parent, LLCTransitIPv480
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv671

All 46 upstreams →

Transit

Downstream networks

inferred

Networks for which AS63399 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 46

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6689
AS1299Arelion Sweden ABTransitIPv4 IPv6329
AS6939Hurricane Electric LLCTransitIPv4 IPv6316
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6258
AS25818CMC NETWORK (PTY) LTDUnclassifiedIPv4 IPv6214
AS3257GTT Communications Inc.TransitIPv4 IPv6153
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6112
AS6461Zayo BandwidthTransitIPv4 IPv698
AS3356Level 3 Parent, LLCTransitIPv480
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv671

All 46 adjacent →

Provenance

Where this comes from

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