Skip to main content
Daily

Issues with joining calls from certain ISPs/regions

Degraded Lasted 1d · started · Daily's page

Level
confirmed
Worst impact
Degraded
Components
Core Call Experience
Regions
us
Down Index
27of 100

What to do

  • Check whether you use Daily Core Call Experience in us. 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 1d it lasted.

    Anything that failed between 2026-06-08 14:32 UTC and 2026-06-09 14:57 UTC may need a replay.
  • Subscribe to Daily's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=daily works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Daily 3

  1. identified

    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. This may result in those users seeing an “Unable to join call” error in the browser when trying to join a call. 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. To work around this, you can encourage your users to use a third-party DNS provider, like Cloudflare or Quad9.

    provider

  2. identified

    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.

    provider

  3. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-7d3cb724a7

Is Daily still down?

No, this incident was resolved 2026-06-09 14:57 UTC. For Daily's live state, see https://down.guide/daily.

How long did it last?

1d, from 2026-06-08 14:32 UTC to 2026-06-09 14:57 UTC, by the times Daily posted.

What was affected?

Daily named Core Call Experience in us.

What caused it?

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

Where does this come from?

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