Daily.co Outage History
17 incidents recorded over the last 365 days, 17 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Daily.co Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 10, 2026 | Continued issues with joining calls from certain ISPs/RegionsThe RegistryDNS.co servers continue to be intermittently unavailable, but AT&T's DNS servers seem to be more responsive. We encourage you to update to daily-js 0.91.0 as soon as possible to avoid future issues for your… | 7h 26m | Resolved |
| Jun 8, 2026 | Issues with joining calls from certain ISPs/regionsCentralNIC 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… | 24h 24m | Resolved |
| Apr 23, 2026 | testtest | 2466h 19m | Resolved |
| Apr 17, 2026 | API and call connection issuesThis incident has been resolved. | 9h 32m | Resolved |
| Apr 10, 2026 | Issues joining callsThis incident has been resolved. | 54 min | Resolved |
| Mar 23, 2026 | Issues with inbound phone callsThis incident has been resolved. We're still collecting more information on the root cause here; we'll update this status post when we have more info. | 58 min | Resolved |
| Mar 16, 2026 | Webhook delivery delaysThis incident has been resolved. | 4h 45m | Resolved |
| Feb 18, 2026 | SIP / PSTN DisruptionThis incident has been resolved. | 4h 23m | Resolved |
| Feb 4, 2026 | Increase in "Failed to load call object bundle" errorsThe issue has been resolved. We’ve seen the number of “Failed to load call object bundle” errors return to normal levels, and call joins are operating as expected. | 8h 16m | Resolved |
| Feb 2, 2026 | Issues with transcriptions and captionsThis incident has been resolved. | 6h 51m | Resolved |
| Jan 26, 2026 | Webhook deliveries delayedThis incident has been resolved. | 4h 37m | Resolved |
| Jan 15, 2026 | Issues starting SIP/PSTN callsThis incident has been resolved. | 39 min | Resolved |
| Jan 13, 2026 | Webhook deliveries delayedWebhook delivery times have returned to normal. | 1h 33m | Resolved |
| Jan 13, 2026 | Issues with PSTN/SIP availabilitySignalWire experienced an outage earlier this morning. Their status site post is here: https://status.signalwire.com/incidents/MJVYwKKYYwbG Our first customer report of problems was at 1:51 AM PST (09:51 UTC). During… | 0 min | Resolved |
| Oct 20, 2025 | Impact from the ongoing AWS us-east-1 outageThis incident has been resolved. | 26h 25m | Resolved |
| Sep 24, 2025 | Dashboard API and webhook logs temporarily disabledThis incident has been resolved. | 27h 4m | Resolved |
| Sep 4, 2025 | Delayed data from the /logs API endpointThis incident has been resolved. | 1h 56m | Resolved |
How to Read This Daily.co Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Daily.co acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Daily.co outage in this window ran 102d 18h, against a mean recovery of 6d 8h. If you depend on Daily.co in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.