Dialpad: Some contact center agents may be experiencing issues with being unable to complete a call wrap-up

What to do

Check whether you use Dialpad Contact Center. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 49m it lasted.
Anything that failed between 2026-08-21 16:21 UTC and 2026-08-21 17:09 UTC may need a replay.
Subscribe to Dialpad's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=dialpad works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

identifiedAug 21, 2026, 4:21 PM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringAug 21, 2026, 4:42 PM UTC
A fix has been implemented and we are monitoring the results. Agents should refresh their application to pick up the change.
provider
resolvedAug 21, 2026, 5:09 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Dialpad still down?

No, this incident was resolved 2026-08-21 17:09 UTC. For Dialpad's live state, see https://down.guide/dialpad.

How long did it last?

49m, from 2026-08-21 16:21 UTC to 2026-08-21 17:09 UTC, by the times Dialpad posted.

What was affected?

Dialpad named Contact Center.

What caused it?

Dialpad hasn't published a root cause. If it does, it shows here.

Where does this come from?

Dialpad's official status page, https://status.dialpad.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.