Daily Outage History
Uptime record, past incidents, and downtime history for Daily.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| June 2026 | 85.2% | 27 | 4 |
| May 2026 | 100% | 31 | 0 |
| April 2026 | 80% | 30 | 6 |
| March 2026 | 100% | 3 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Mar 29
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
June 2026
Continued issues with joining calls from certain ISPs/Regions
Started: Jun 10, 7:20 PM
monitoring
daily-js 0.91.0 is now available on npm and GitHub. If your app uses call object mode, you can update your dependency to that version and redeploy, and this issue should be resolved for you. We're publishing an update to our networking guide soon, but in the meantime, anything that mentions a `.daily.co` hostname in that doc is also available at `.dailywebrtc.com` and `.dailywebrtc.net`.
We'll have updates for embedded Prebuilt and direct link customers soon. We'll leave this incident open w...
Jun 10, 10:07 PM
identified
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, ...
Jun 10, 7:32 PM
identified
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.
Jun 10, 7:20 PM
Issues with joining calls from certain ISPs/regions
Started: Jun 8, 2:32 PM
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.
Jun 8, 8:12 PM
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 c...
Jun 8, 2:32 PM
April 2026
test
Started: Apr 23, 1:42 AM
investigating
test
Apr 23, 1:42 AM
API and call connection issues
Started: Apr 17, 1:33 PM
identified
Our tests just confirmed that DNS resolution is no longer returning errors for .co domains in our tests. This issue has been resolved!
Apr 17, 11:04 PM
identified
The rate of bundle download failures has decreased, but it's also tracking our overall usage volume through the day. The number of affected users appears to be very small, but we still have tests that can replicate the failure. Unfortunately this is completely out of our control. If you have users that are continuing to be affected, you can suggest that they use Google's or Quad9's DNS servers at 1.1.1.1 or 9.9.9.9.
Apr 17, 9:46 PM
identified
Cloudflare has resolved their status incident, but we're unsure if that means the underlying issue is resolved. We're continuing to monitor our own error rates and health checks.
Apr 17, 8:06 PM
identified
Cloudflare has posted that they've implemented a fix, and they are monitoring the results. We're still not certain that Cloudflare is the actual root cause of 100% of our affected users, but we'll be monitoring error rates.
Apr 17, 6:26 PM
identified
The .co registry appears to be experiencing issues. Cloudflare's recursive DNS is affected (and they've acknowledged it). Many regional ISPs, such as AT&T in the southeast US, rely on Cloudflare's DNS to power their own DNS.
Unlike Cloudflare, other DNS providers, like Google and Quad9, are serving .co records from stale cache. If they stop doing this, then anyone using those DNS services will start to experience these same failures.
This won't be fully resolved until the .co registry comes...
Apr 17, 6:13 PM
identified
Cloudflare has posted an incident concerning intermittent DNS failures for .co domains: https://www.cloudflarestatus.com/incidents/z3b5zxjtp6g1
This aligns with the troubleshooting we've done so far. Some internet discussions suggest that it can be somewhat ISP-dependent, but this is unconfirmed. If this is indeed related to the .co domain itself, it would mean that it affects participants' ability to join calls, but it could also affect the ability to make API requests to api.daily.co. Upd...
Apr 17, 3:50 PM
identified
We've confirmed through several different end users that this is a DNS issue. Affected users from multiple regions have been able to join calls by pointing DNS to Google or CloudFlare, using IPs like 1.1.1.1 or 8.8.8.8 for DNS. Obviously, this solution doesn't scale; we're working with AWS to identify the root cause of the DNS resolution issue for c.daily.co.
Apr 17, 2:56 PM
identified
We're receiving reports of a few other regions experiencing similar connection issues. If you're monitoring client errors and you see messages that start with "Failed to load call object bundle https://c.daily.co/....", you're being affected by this. We're working with AWS to get to the bottom of this.
Apr 17, 2:06 PM
identified
We've identified an issue that's causing some users to fail to join calls. The daily-js library has to download a bundle of additional JavaScript as part of joining a call. This bundle is downloaded from c.daily.co, which is using Amazon's CloudFront CDN. They aren't reporting issues yet, but we're engaging with their support to figure out why this is happening.
Apr 17, 1:54 PM
investigating
We're receiving reports of some users having problems connecting to Daily calls. It seems to be localized to the Texas area. We're investigating.
Apr 17, 1:33 PM
Issues joining calls
Started: Apr 10, 3:36 PM
monitoring
There was a sudden increase in activity across several databases. We've addressed the cause of the issue, and platform metrics are returning to normal. We're continuing to monitor for any further issues.
Apr 10, 3:45 PM
investigating
We're seeing an elevated rate of errors for API requests and room joins. We're addressing it right now.
Apr 10, 3:36 PM
March 2026
Issues with inbound phone calls
Started: Mar 23, 8:18 PM
monitoring
It seems that SignalWire has resolved their issue. We're monitoring for any other problems.
Mar 23, 8:31 PM
investigating
SignalWire has identified an issue causing problems with incoming and outgoing PSTN/SIP calls for Daily customers.
If you're making dialout calls, you may see an error that says "DialOut stopped: Remote busy or Remote did not answer or Remote ended the call".
If you're using dialin, you may hear a message that says "the number you have dialed is not configured correctly and cannot receive calls" or something similar.
Mar 23, 8:29 PM
investigating
We're investigating elevated error rates for incoming PSTN/SIP calls.
Mar 23, 8:18 PM
Webhook delivery delays
Started: Mar 16, 5:12 PM
monitoring
We've identified an issue with the webhook system that was causing brief delays when finding meeting start and end events for webhooks. We've addressed that issue. Webhook delivery time was only minimally impacted during the event, and it has returned to normal as of about 15 minutes ago.
Mar 16, 6:31 PM
investigating
We're investigating an issue that may be causing delayed delivery for some webhooks.
Mar 16, 5:12 PM