Skip to main content

AS63399

DIALPAD

Dialpad, Inc.

Registry

Authoritative registration data

AS number
63399
Name
DIALPAD
Organisation
Dialpad, Inc.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

35

IPv6 prefixes

14

Total announced

49

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS63399
170.10.192.0/19 IPv4 /19 not checked
209.127.80.0/20 IPv4 /20 not checked
170.10.194.0/23 IPv4 /23 not checked
170.10.196.0/23 IPv4 /23 not checked
170.10.198.0/23 IPv4 /23 not checked
170.10.200.0/23 IPv4 /23 not checked
209.127.82.0/23 IPv4 /23 not checked
209.127.84.0/23 IPv4 /23 not checked
209.127.86.0/23 IPv4 /23 not checked
103.35.126.0/24 IPv4 /24 RPKI valid
170.10.206.0/24 IPv4 /24 not checked
170.10.207.0/24 IPv4 /24 not checked
170.10.208.0/24 IPv4 /24 not checked
170.10.209.0/24 IPv4 /24 not checked
170.10.210.0/24 IPv4 /24 not checked
170.10.211.0/24 IPv4 /24 not checked
170.10.212.0/24 IPv4 /24 not checked
170.10.213.0/24 IPv4 /24 not checked
170.10.214.0/24 IPv4 /24 not checked
170.10.215.0/24 IPv4 /24 not checked
170.10.216.0/24 IPv4 /24 RPKI valid
170.10.217.0/24 IPv4 /24 not checked
170.10.219.0/24 IPv4 /24 not checked
185.91.8.0/24 IPv4 /24 not checked
185.91.9.0/24 IPv4 /24 not checked
209.127.80.0/24 IPv4 /24 not checked
209.127.81.0/24 IPv4 /24 not checked
209.127.88.0/24 IPv4 /24 not checked
209.127.89.0/24 IPv4 /24 not checked
209.127.90.0/24 IPv4 /24 not checked
209.127.91.0/24 IPv4 /24 RPKI valid
209.127.92.0/24 IPv4 /24 not checked
209.127.93.0/24 IPv4 /24 not checked
209.127.94.0/24 IPv4 /24 RPKI valid
209.127.95.0/24 IPv4 /24 not checked
2a05:e580::/29 IPv6 /29 RPKI valid
2a05:e580:100::/40 IPv6 /40 not checked
2a05:e580:200::/40 IPv6 /40 RPKI valid
2a05:e580:300::/40 IPv6 /40 RPKI valid
2a05:e580:400::/40 IPv6 /40 not checked
2a05:e580:500::/40 IPv6 /40 not checked
2a05:e580:600::/40 IPv6 /40 not checked
2a05:e580:700::/40 IPv6 /40 RPKI valid
2a05:e580:800::/40 IPv6 /40 not checked
2a05:e580:900::/40 IPv6 /40 not checked
2a05:e580:a00::/40 IPv6 /40 not checked
2a05:e580:b00::/40 IPv6 /40 not checked
2a05:e580:c00::/40 IPv6 /40 not checked
2a05:e580:d00::/40 IPv6 /40 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS63399
Address families
BBIX Osaka 10,000 Mbps IPv4 · IPv6
BBIX Tokyo 1,000 Mbps IPv4 · IPv6
ChIX 1,000 Mbps IPv4 · IPv6
DE-CIX Dallas: DE-CIX Dallas Peering LAN 200,000 Mbps IPv4 · IPv6
DE-CIX New York: DE-CIX New York Peering LAN 200,000 Mbps IPv4 · IPv6
Digital Realty Dallas 10,000 Mbps IPv4 · IPv6
Equinix Chicago 10,000 Mbps IPv4 · IPv6
Equinix Dallas 10,000 Mbps IPv4 · IPv6
Equinix New York 10,000 Mbps IPv4 · IPv6
Equinix Osaka 1,000 Mbps IPv4 · IPv6
Equinix San Jose 10,000 Mbps IPv4 · IPv6
Equinix Sydney 1,000 Mbps IPv4 · IPv6
HKIX: HKIX Peering LAN 1,000 Mbps IPv4 · IPv6
LINX LON1: Main 10,000 Mbps IPv4 · IPv6
NAPAfrica IX Johannesburg: Peering 10,000 Mbps IPv4 · IPv6
SGIX: Peering LAN 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS63399 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

49 networks seen before AS63399 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS63399 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

35 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.