Is Dialpad Down?

No — Dialpad is up

Reachable from all 8 checked regions

Average response time: 174ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.dialpad.com

Dialpad uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

131ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 22 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

22-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

100ms

DNS 1ms TCP 2ms TLS 12ms TTFB 88ms

arn

166ms

DNS 0ms TCP 1ms TLS 18ms TTFB 130ms

bom

323ms

DNS 3ms TCP 5ms TLS 11ms TTFB 308ms

cdg

155ms

DNS 1ms TCP 1ms TLS 9ms TTFB 143ms

dfw

272ms

DNS 0ms TCP 1ms TLS 9ms TTFB 263ms

ewr

86ms

DNS 0ms TCP 2ms TLS 8ms TTFB 75ms

fra

114ms

DNS 0ms TCP 1ms TLS 12ms TTFB 106ms

gru

99ms

DNS 7ms TCP 3ms TLS 13ms TTFB 85ms

iad

179ms

DNS 1ms TCP 6ms TLS 21ms TTFB 167ms

What Dialpad does

Dialpad is a cloud phone and contact centre platform: business calling, messaging, meetings and an AI layer that transcribes and assists on live calls. Support and sales teams run their inbound queues on it, so an outage is not a productivity inconvenience but a business phone line that stops ringing while customers keep dialling.

What an outage looks like

Inbound calls stop reaching agents, or ring and drop before connecting; Dialpad tracks inbound and outbound telephony separately, so one direction can fail alone. Toll-free numbers can break while local numbers keep working, because they run over different carrier paths. Contact centre queues stall, SMS stops sending, and meetings fail to start or lose audio mid-call.

What to do about it

Check status.dialpad.com and read the specific component: inbound calls, outbound calls, toll-free numbers, messaging, Contact Center and Meetings are reported separately, and Dialpad also lists its Google Cloud Platform dependency. If inbound is failing, forward the affected numbers to a mobile so customers still reach someone. Carrier-side problems can affect one number range and leave the rest working.

Is it down for everyone, or just you?

If this page says Dialpad is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Dialpad outage FAQ

Is Dialpad down or is it just my toll-free number?

Dialpad reports local numbers and toll-free numbers as separate carrier network components, and they genuinely fail independently. A toll-free incident leaves direct-dial numbers answering normally, which is why colleagues often report the phones as fine. Test a local number and the toll-free number from an outside line, then match what you see against status.dialpad.com.

Can callers still reach us during a Dialpad outage?

Not through Dialpad if the telephony components are down, and callers usually hear ringing or a failure tone rather than anything that tells them to try later. Forwarding affected numbers to mobiles is the fastest mitigation and does not depend on the Dialpad app working. Set the forwarding early rather than after the queue has backed up.

Does a Dialpad outage affect meetings and messaging too?

Not necessarily. Meetings, Messaging, Contact Center and the core telephony infrastructure are tracked as separate components, so video meetings can run normally while inbound calling is failing, or the reverse. Check the individual component rather than the overall banner, then move the urgent conversation to whichever channel is reported healthy.

Why does Dialpad list Google Cloud Platform on its status page?

Dialpad runs on Google Cloud and tracks it as a dependency component, so a Google Cloud incident can surface as a Dialpad one. That is useful context during an outage: if the underlying platform is the cause, the fix is not something Dialpad support can accelerate, and recovery tends to follow the upstream provider's timeline.

How we measure this

We request Dialpad's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Dialpad publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Dialpad goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required