Daily incident
Issues with joining calls from certain ISPs/regions
Daily experienced a minor incident on June 8, 2026 affecting Core Call Experience, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 08, 2026, 02:32 PM UTC
We've identified an issue that's preventing some users from being able to join calls, resulting in errors like "Unable to join call" in the browser. This is being caused by failures from the DNS servers that serve the .co TLD itself. Several third-party DNS providers like Google, Cloudflare, and Quad9 are working around this in order to continue to make .co domains available. But users that are using their ISP's DNS service (specifically AT&T users in the southeast US and/or Texas) are experiencing intermittent problems accessing any .co domain, including daily.co. Unfortunately, the only workaround is to encourage your users to use a third-party DNS provider, like Cloudflare or Quad9. We're working on addressing this long-term.
- identified Jun 08, 2026, 08:12 PM UTC
We are working on implementing a fallback to a .com domain so that users on ISPs that are not fixing this will not see any issues starting calls.
- resolved Jun 09, 2026, 02:57 PM UTC
CentralNIC confirmed that there was indeed an issue with the .co nameservers, and they resolved it at approximately 06:30 UTC today. Our monitoring of both their DNS servers and downstream providers confirmed this. We're continuing to work urgently on updating our infrastructure to make our services available on alternate hostnames. We'll post updates to our Networking Guide when we do: https://docs.daily.co/guides/privacy-and-security/corporate-firewalls-nats-allowed-ip-list We'll also provide a root cause analysis for this incident in the next few days.