Issues with logging and telemetry

What to do

• Check whether you use Daily Dashboard, Core Call Experience. 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 2h 51m it lasted.

  Anything that failed between 2025-06-12 18:56 UTC and 2025-06-12 21:47 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 5

1. investigatingJun 12, 2025, 6:39 PM UTC

   Daily is being affected by widespread internet outages in authentication services. This is currently affecting our ability to collect or view some call metrics. We'll post more as soon as we have more information.

   provider

2. identifiedJun 12, 2025, 6:56 PM UTC

   This appears to be related to the Google Cloud outage posted here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW We'll post here as we learn more.

   provider

3. identifiedJun 12, 2025, 8:06 PM UTC

   We're seeing some increases in response time from our internal API endpoint that returns connection information to daily-js. This may be causing "room lookup timed out" errors for users attempting to join calls. We believe this is related to the ongoing GCP incident.

   provider

4. identifiedJun 12, 2025, 8:49 PM UTC

   We had a brief spike in response time, but platform operations appear normal since approximately 20:05 UTC. We're continuing to monitor for any follow-on effects, and we'll leave this status post open until various upstream providers close their respective status incidents.

   provider

5. resolvedJun 12, 2025, 9:47 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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