doxy.me experienced a major incident on December 1, 2021 affecting Doxy.me webpages, lasting 126d 22h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Dec 01, 2021, 04:16 PM UTC
We have identified an issue with Firefox failing to send the audio and video from the device after the first few minutes of a call. The individual using Firefox can still see and hear the other participant(s) on the call during this error. The person using Firefox can no longer be seen or heard. Temporary Workaround: Switch to another supported browser (Chrome, Safari, Edge) for the time being.
- monitoring Dec 03, 2021, 02:39 PM UTC
We deployed a fix that is resolving the issue in Chrome and Firefox. We are continuing to look into the publishing issue with Safari browsers. If you use Safari as your default browser, please continue to use Chrome for now.
- monitoring Dec 07, 2021, 05:33 PM UTC
We have delivered another update that should resolve the remaining problems with the media publishers being destroyed on Safari during a call. Our teams will continue to monitor the situation until issues are confirmed to be resolved.
- monitoring Dec 10, 2021, 04:58 PM UTC
We are continuing to see reports with Safari’s media stream being destroyed during calls and we continue to investigate the issue with our media vendor. We recommend using either Chrome or Firefox as we are no longer receiving reports of this problem with these browsers. We see fewer issues being reported after updating the experimental feature setting within Safari. If you’d prefer to continue to use Safari, please update the WebRTC Platform UDP Socket setting: 1. On iPhone or iPad, open the device’s settings. 2. Select Safari > Advanced > Experimental Features. 3. Disable WebRTC Platform UDP Sockets (switch toggle from Green to Gray). 4. Close Safari and open it again. 5. Return to doxy.me.
- monitoring Dec 21, 2021, 09:16 PM UTC
We have rolled back updates from our third party vendor to reduce the occurrences of this issue. We are pending another update from the vendor as we continue to work together to resolve this problem. Please continue to use the workarounds listed.
- resolved Apr 07, 2022, 02:26 PM UTC
We have implemented our vendor's fix for this incident and are no longer seeing related user reports.