# Issues answering calls on Google Chrome and MS Edge using the external notification

- Provider: [Dialpad](https://down.guide/providers/dialpad)
- Confidence: Confirmed
- Impact: Degraded
- lasted 2d 21h
- started 2025-04-11 21:13 UTC
- Application
- id: DWN-d5c79c0a24
- Official page: https://stspg.io/hfjvgjlbd8s3

## Updates from Dialpad
### 2025-04-11 21:13 UTC: identified
We've identified the issue. Workaround is to use the notification pop up within the dialpad.com browser tab

### 2025-04-12 01:13 UTC: monitoring
A fix has been pushed to production and we're currently monitoring

### 2025-04-14 18:36 UTC: resolved
No issues were found and the incident is resolved

From the builder: does your app depend on Dialpad? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=dialpad) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Dialpad.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-d5c79c0a24), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
