Daily experienced a critical incident on April 9, 2025 affecting SIP/PSTN, lasting 9h 32m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 09, 2025, 12:15 PM UTC
We're seeing elevated error rates from our SIP/PSTN provider. If you're creating rooms with dial-in support and getting errors, you may want to retry creating those rooms without dial-in, and then add dial-in with an update REST request.
- identified Apr 09, 2025, 12:53 PM UTC
Our SIP/PSTN provider has identified an issue and they're deploying a fix. In the meantime, you should still be able to create Daily rooms without provisioning SIP/PSTN.
- identified Apr 09, 2025, 01:50 PM UTC
We're continuing to monitor an issue from our SIP/PSTN provider. The rest of the Daily platform is unaffected. If you're getting an error when trying to create a room, you can remove the dialout_enabled property from the room creation request and try again.
- identified Apr 09, 2025, 02:26 PM UTC
We're still monitoring. In addition to dialout_enabled, you'll need to remove other room properties related to SIP/PSTN, dialin, and/or dialout to create rooms.
- identified Apr 09, 2025, 05:22 PM UTC
We're still waiting on Signalwire to restore service.
- identified Apr 09, 2025, 05:46 PM UTC
We've been told we should be back online after a hotfix at approximately 18:00 UTC, or 15 minutes from now. We'll post another update as soon as we have more info.
- monitoring Apr 09, 2025, 06:53 PM UTC
Signalwire has restored service, but we're still seeing some error responses from their API. We believe the majority of room creation failure issues have been resolved. We'll post here again when we've handled this last issue.
- monitoring Apr 09, 2025, 08:12 PM UTC
We're still waiting on some additional fixes from Signalwire. Room creation with dial-in/dial-out is working, but you still may experience problems updating dial-in/dial-out settings for existing rooms. Daily Bots and Pipecat Cloud users should be unaffected.
- resolved Apr 09, 2025, 09:48 PM UTC
This incident has been resolved.