Daily incident

Continued issues with joining calls from certain ISPs/Regions

Minor Ongoing View vendor source →

Daily is currently experiencing a minor incident affecting Core Call Experience, which began 2h ago. The vendor's full update timeline is below.

Started
Jun 10, 2026, 07:20 PM UTC
Resolved
Ongoing
Duration
● 2h 14m
Detected by Pingoru
Jun 10, 2026, 07:20 PM UTC

Affected components

Core Call Experience

Update timeline

  1. identified Jun 10, 2026, 07:20 PM UTC

    We're seeing a recurrence of the problems with RegistryDNS.co and AT&T DNS from Monday. Users trying to join calls from affected regions using ISP DNS may get "Unable to join call" errors. We know specifically that AT&T DNS servers 68.94.157.1 and 68.94.156.1 are affected. We've been working hard on solving this problem since the incident on Monday. We're releasing daily-js 0.91.0 shortly to address this.

  2. identified Jun 10, 2026, 07:32 PM UTC

    We expect to have daily-js 0.91.0 available within the next 60 to 90 minutes. The update includes automated failover to `dailywebrtc.com` or `dailywebrtc.net` if `daily.co` is unreachable. If you haven't updated daily-js in a while, you can do preliminary testing with 0.90.0 in order to be ready to release an update with 0.91 as soon as it's ready. 0.91 will only contain this feature, as well as a few dependency version updates for security. If you have customers with restrictive networks, they may need to add `*.dailywebrtc.com` and `*.dailywebrtc.net` to their firewall/security allowlists. These domains are relatively new, so they may be flagged by Cisco app firewalls and similar security appliances.