Update - We are continuing to monitor for any further issues.
Jan 11, 17:45 EST
Update - In a continuing effort to mitigate the low audio bug, we have found that following these steps helps resolve the issue during a call.

When the patient says audio is low:
1. Copy this link and put it in your chat box: https://ccrma.stanford.edu/~jos/mp3/pno-cs.mp3
2. Ask the patient to click the link. When they click it they will hear a piano sound AND the volume will increase.
3. Ask them to close that tab and go back to the tab with doxy.me in it.
4. If the camera stops (this may happen occasionally) ask them to simply turn the camera off and on again to bring back the video.
5. The audio level should be back to normal now.
Jan 11, 17:32 EST
Update - Apple has started rolling out iOS 15.2 which they claim has an improvement (not a permanent fix) for the Low Audio bug. They state that the audio is now coming out of both the ear piece and loudspeaker, so the audio volume should be louder after the update. Please note this is not the long term fix. Please check your device for this update.

If you have a headset or AirPods that you can use, we recommend using those if you continue to experience problems with the low audio.
Dec 21, 16:17 EST
Update - We are aware of a bug introduced by the deployment of Safari 15 that is impacting all WebRTC systems. Many Safari 15 users may experience very low or hard to hear audio from their clients while on calls with their clients or providers. If you experience this issue during a call, please try another internet browser such as Google Chrome or Firefox.

We are working internally and with our vendors to see if there is anything we can do to help mitigate the issue. Our Vendor has confirmed that they have filed a bug with Apple. We are also anticipating the issues will be resolved in an upcoming update by Apple. We do not have any information from Apple regarding an expected fix date.

We have identified a couple workarounds that is having some success with increasing the volume during sessions:
Workaround #1
1) Start a call
2) Open iOS settings > Accessibility > Hearing devices
3) Hearing Aid Compatibility> Toggle On/Off. The end result of leaving the setting on or off does not matter for the doxy.me call, just flip the setting.

Note: Workaround 1 only impacts the current call. These steps would need to be repeated for your following calls.

Workaround #2
1) Open a new browser tab in that browser (DO NOT close the doxy tab)
2) Pull up http://youtube.com/ in the new tab
3) Select anything and play it for a few seconds
4) Close the tab with youtube in it and go back to Doxy tab
5) The Volume should be remain at the normal higher volume
Nov 1, 09:34 EDT
Monitoring - We are aware of a bug introduced by the deployment of Safari 15 that is impacting all WebRTC systems. Many Safari 15 users may experience very low or hard to hear audio from their clients while on calls with their clients or providers. If you experience this issue during a call, please try another internet browser such as Google Chrome or Firefox.

We are working internally and with our vendors to see if there is anything we can do to help mitigate the issue. Our Vendor has confirmed that they have filed a bug with Apple. We are also anticipating the issues will be resolved in an upcoming update by Apple. We do not have any information from Apple regarding an expected fix date.

We have identified a workaround that is having some success with increasing the volume during sessions:
1) Open a new browser tab in that browser (DO NOT close the doxy tab)
2) Pull up http://youtube.com/ in the new tab
3) Select anything and play it for a few seconds
4) Close the tab with youtube in it and go back to Doxy tab
5) The Volume should be remain at the normal higher volume
Oct 7, 15:20 EDT
Identified - We have identified a setting that is enabled by default on updated iOS devices that is preventing doxy.me calls from connecting. To correct this, please disable the 'WebRTC PlatformUDP Sockets' setting.

On iPhone or iPad:
1. Open up the device’s settings
2. Navigate to Safari > Advanced > Experimental Features
3. Disable WebRTC Platform UDP Sockets.
4. Close Safari and open it again.
5. Log back into doxy.me
Dec 2, 09:19 EST
Update - 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.
Dec 21, 16:16 EST
Update - 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.
Dec 10, 11:58 EST
Update - 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.
Dec 7, 12:33 EST
Monitoring - 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.
Dec 3, 09:39 EST
Identified - 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.
Dec 1, 11:16 EST
Monitoring - Google Chrome has confirmed the fix for this issue will be deployed with Version 98. In the meantime, the workaround will still be needed:

Android 12 users are able to fix this with these steps:
1) Go to chrome://flags
2) under "Search Flags", enter "hardware"
3) Disable the "WebRTC Hardware Video Encoding" Setting
4) Check back in and restart the call.
Nov 29, 15:22 EST
Investigating - We have identified an issue where the video from Android 12 devices appears as scrambled lines instead of a clear picture. Audio is not impacted and comes through normally.

Android 12 users are able to fix this with these steps:
1) Go to chrome://flags
2) under "Search Flags", enter "hardware"
3) Disable the "WebRTC Hardware Video Encoding" Setting
4) Check back in and restart the call.
Nov 8, 16:06 EST

About This Site

Doxy.me support publishes our most up-to-the-minute information on service availability below. Check back here any time to get current status information, or subscribe to email updates to be notified of interruptions to each individual service. If you are experiencing a real-time, operational issue with one of our services that is not described below, please inform us by emailing support@doxy.me

Doxy.me API ? Operational
90 days ago
99.98 % uptime
Today
Doxy.me webpages ? Operational
90 days ago
99.99 % uptime
Today
Discussion board ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Doxy.me Homepage Response Time ?
Fetching
Doxy.me API Response Time ?
Fetching
Past Incidents
Jan 18, 2022

No incidents reported today.

Jan 17, 2022

No incidents reported.

Jan 16, 2022

No incidents reported.

Jan 15, 2022

No incidents reported.

Jan 14, 2022

No incidents reported.

Jan 13, 2022

No incidents reported.

Jan 12, 2022

No incidents reported.

Jan 11, 2022
Resolved - This incident has been resolved.
Jan 11, 07:40 EST
Monitoring - A fix has been implemented and we are monitoring the results for the next 30 minutes. Patients should be able to check-in as usual.
Jan 11, 06:55 EST
Identified - We have identified an issue where patients are not able to check-in. A fix is in progress, and this is expected to be resolved in the next 5 minutes.
Jan 11, 06:32 EST
Jan 10, 2022

No incidents reported.

Jan 9, 2022

No incidents reported.

Jan 8, 2022

No incidents reported.

Jan 7, 2022
Postmortem - Read details
Jan 13, 16:47 EST
Resolved - This incident has been resolved. Our team is working on the post-mortem which will be posted next week.
Jan 7, 14:40 EST
Monitoring - We are seeing that our API is continuing to stabilize. We are looking into what caused this spike while we continue to monitor the incident.
Jan 7, 12:25 EST
Investigating - We are looking into the reports of clients being unable to log into doxy.me. We will provide updates within the next 30 minutes.
Jan 7, 12:12 EST
Jan 6, 2022

No incidents reported.

Jan 5, 2022

No incidents reported.

Jan 4, 2022

No incidents reported.