Snapshot 19943
Normalized text
Scripts and page chrome removed; this is what change detection compares.
<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/"> <channel> <title>Whereby Status - Incident history</title> <link>https://wherebystatus.com</link> <description>Whereby</description> <pubDate>Tue, 22 Sep 2026 17:43:07 +0000</pubDate> <item> <title>Customer insights (dashboard and api) - degraded performance</title> <description> Type: Incident Duration: 2 hours and 2 minutes Affected Components: Admin dashboard, Embedded API Sep 22, 17:43:07 GMT+0 - Investigating - We are currently investigating failed and slow responses from our customer insights api Sep 22, 18:48:23 GMT+0 - Monitoring - We have cleared out some long-running jobs affecting the performance, monitoring.... Sep 22, 19:45:01 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 2 hours and 2 minutes</p> <p><strong>Affected Components:</strong> , </p> <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>17:43:07</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating failed and slow responses from our customer insights api.</p> <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>18:48:23</var> GMT+0</small><br><strong>Monitoring</strong> - We have cleared out some long-running jobs affecting the performance, monitoring.....</p> <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>19:45:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Tue, 22 Sep 2026 17:43:07 +0000</pubDate> <link>https://wherebystatus.com/incident/cmucypv0g1iox1nruwz58juy3</link> <guid>https://wherebystatus.com/incident/cmucypv0g1iox1nruwz58juy3</guid> </item> <item> <title>Issues when joining room</title> <description> Type: Incident Duration: 4 minutes Affected Components: Meeting rooms Sep 14, 09:59:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 14, 10:03:00 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 4 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>09:59:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Sep <var data-var='date'> 14</var>, <var data-var='time'>10:03:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Mon, 14 Sep 2026 09:59:00 +0000</pubDate> <link>https://wherebystatus.com/incident/cmu14jpc50bja0wl0tgch1boy</link> <guid>https://wherebystatus.com/incident/cmu14jpc50bja0wl0tgch1boy</guid> </item> <item> <title>Whereby hosted recordings are unavailable</title> <description> Type: Incident Duration: 36 minutes Affected Components: Meeting rooms Sep 1, 12:16:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 1, 12:52:00 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 36 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>12:16:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>12:52:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Tue, 1 Sep 2026 12:16:00 +0000</pubDate> <link>https://wherebystatus.com/incident/cmtio4mh706ck1bmf3xdeulnm</link> <guid>https://wherebystatus.com/incident/cmtio4mh706ck1bmf3xdeulnm</guid> </item> <item> <title>Unable to access dashboard pages</title> <description> Type: Incident Duration: 6 minutes Affected Components: whereby.com, Admin dashboard May 5, 10:16:27 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 5, 10:22:26 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 6 minutes</p> <p><strong>Affected Components:</strong> , </p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>10:16:27</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 5</var>, <var data-var='time'>10:22:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Tue, 5 May 2026 10:16:27 +0000</pubDate> <link>https://wherebystatus.com/incident/cmosh46s006d182bdw142988n</link> <guid>https://wherebystatus.com/incident/cmosh46s006d182bdw142988n</guid> </item> <item> <title>Streaming Unavailable</title> <description> Type: Incident Duration: 55 minutes Affected Components: Meeting rooms Apr 29, 12:51:52 GMT+0 - Investigating - We are currently investigating an incident affecting streaming for all users. Streaming is unavailable at this time. Apr 29, 13:47:05 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 55 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>12:51:52</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an incident affecting streaming for all users. Streaming is unavailable at this time..</p> <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>13:47:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Wed, 29 Apr 2026 12:51:52 +0000</pubDate> <link>https://wherebystatus.com/incident/cmok20y7201e9vsv3vizmzziw</link> <guid>https://wherebystatus.com/incident/cmok20y7201e9vsv3vizmzziw</guid> </item> <item> <title>Customer Insights Dashboard – Stale Data</title> <description> Type: Incident Duration: 4 days, 20 hours and 18 minutes Affected Components: Admin dashboard Mar 25, 14:09:22 GMT+0 - Identified - The third party provider has found the root cause of the issue on their side and they are actively working on a fix. We will provide further updates as the situation progresses. Mar 28, 01:00:00 GMT+0 - Resolved - This incident has been resolved. Mar 23, 11:22:22 GMT+0 - Identified - **What's happening** Some customers may currently be seeing outdated data in the Customer Insights section of their dashboard. **Impact** \- Customer Insights data does not reflect the most recent activity \- Insights API is also affected. \- No data has been lost. All data will be available after the incident is resolved \- All other platform functionality is unaffected **What we're doing** We have identified the root cause as a bug introduced by a third-party maintenance update. We have raised a ticket with the provider and they are actively investigating. We will provide updates as the situation progresses. Mar 24, 13:56:57 GMT+0 - Identified - We are continuing to work on a fix for this incident together with the third party provider. Mar 23, 11:00:00 GMT+0 - Investigating - Customers may currently be seeing outdated data in the Customer Insights section of their dashboard. **Impact** \- Customer Insights data does not reflect the most recent activity \- Insights API is also affected. \- No data has been lost. All data will be available after the incident is resolved \- All other platform functionality is unaffected **What we're doing** We are currently investigating the root cause. Mar 26, 13:53:25 GMT+0 - Identified - We are continuing to work on a fix for this incident. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 4 days, 20 hours and 18 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>14:09:22</var> GMT+0</small><br><strong>Identified</strong> - The third party provider has found the root cause of the issue on their side and they are actively working on a fix. We will provide further updates as the situation progresses..</p> <p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>11:22:22</var> GMT+0</small><br><strong>Identified</strong> - **What's happening** Some customers may currently be seeing outdated data in the Customer Insights section of their dashboard. **Impact** \- Customer Insights data does not reflect the most recent activity \- Insights API is also affected. \- No data has been lost. All data will be available after the incident is resolved \- All other platform functionality is unaffected **What we're doing** We have identified the root cause as a bug introduced by a third-party maintenance update. We have raised a ticket with the provider and they are actively investigating. We will provide updates as the situation progresses..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>13:56:57</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident together with the third party provider..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Investigating</strong> - Customers may currently be seeing outdated data in the Customer Insights section of their dashboard. **Impact** \- Customer Insights data does not reflect the most recent activity \- Insights API is also affected. \- No data has been lost. All data will be available after the incident is resolved \- All other platform functionality is unaffected **What we're doing** We are currently investigating the root cause..</p> <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>13:53:25</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> ]]> </content:encoded> <pubDate>Mon, 23 Mar 2026 11:00:00 +0000</pubDate> <link>https://wherebystatus.com/incident/cmn34z90i11u2hvwr3sd5lumd</link> <guid>https://wherebystatus.com/incident/cmn34z90i11u2hvwr3sd5lumd</guid> </item> <item> <title>Missing insight data on the admin dashboard</title> <description> Type: Incident Duration: 1 hour and 22 minutes Affected Components: Admin dashboard Mar 3, 12:30:45 GMT+0 - Investigating - We are investigating the issue. Mar 3, 13:00:00 GMT+0 - Identified - We have identified the issue and we are continuing to work on a fix for this incident. Mar 3, 13:53:12 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour and 22 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>12:30:45</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating the issue..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue and we are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>13:53:12</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Tue, 3 Mar 2026 12:30:45 +0000</pubDate> <link>https://wherebystatus.com/incident/cmmanwpis0c9gw0jvjjh2bulu</link> <guid>https://wherebystatus.com/incident/cmmanwpis0c9gw0jvjjh2bulu</guid> </item> <item> <title>Service Disruption: Recordings, Captions, and Transcriptions</title> <description> Type: Incident Duration: 53 minutes Affected Components: Meeting rooms Feb 20, 11:17:44 GMT+0 - Investigating - We are currently investigating this incident. Feb 20, 12:09:04 GMT+0 - Identified - Feb 20, 12:10:41 GMT+0 - Resolved - This incident has been resolved. Feb 20, 12:09:35 GMT+0 - Monitoring - Whereby-hosted Recordings, Transcriptions, and Captions were unavailable starting 10:47am UTC. Sessions using Whereby-hosted storage that were already in progress at this time may have incomplete Recordings or Transcriptions. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 53 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>11:17:44</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>12:09:04</var> GMT+0</small><br><strong>Identified</strong> - .</p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>12:10:41</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>12:09:35</var> GMT+0</small><br><strong>Monitoring</strong> - Whereby-hosted Recordings, Transcriptions, and Captions were unavailable starting 10:47am UTC. Sessions using Whereby-hosted storage that were already in progress at this time may have incomplete Recordings or Transcriptions..</p> ]]> </content:encoded> <pubDate>Fri, 20 Feb 2026 11:17:44 +0000</pubDate> <link>https://wherebystatus.com/incident/cmluspz3f0inlgoe2bahk9uqc</link> <guid>https://wherebystatus.com/incident/cmluspz3f0inlgoe2bahk9uqc</guid> </item> <item> <title>New signups are unable to join rooms</title> <description> Type: Incident Duration: 44 minutes Affected Components: Meeting rooms Feb 16, 16:00:38 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 16, 16:44:38 GMT+0 - Resolved - </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 44 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>16:00:38</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>16:44:38</var> GMT+0</small><br><strong>Resolved</strong> - .</p> ]]> </content:encoded> <pubDate>Mon, 16 Feb 2026 16:00:38 +0000</pubDate> <link>https://wherebystatus.com/incident/cmlpfqxm1025lm9vl6pqsm05u</link> <guid>https://wherebystatus.com/incident/cmlpfqxm1025lm9vl6pqsm05u</guid> </item> <item> <title>primary languages transcriptions and captions are not working</title> <description> Type: Incident Duration: 1 hour and 8 minutes Affected Components: Meeting rooms Nov 15, 13:00:13 GMT+0 - Investigating - Our third party provider has an incident. We are currently investigating the incident. Nov 15, 13:25:15 GMT+0 - Identified - We have identified an alternative solution until our provider solves the incident on their side. We are currently working on it. Nov 15, 14:08:41 GMT+0 - Resolved - The fix has been deployed and the incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour and 8 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Nov <var data-var='date'> 15</var>, <var data-var='time'>13:00:13</var> GMT+0</small><br><strong>Investigating</strong> - Our third party provider has an incident. We are currently investigating the incident..</p> <p><small>Nov <var data-var='date'> 15</var>, <var data-var='time'>13:25:15</var> GMT+0</small><br><strong>Identified</strong> - We have identified an alternative solution until our provider solves the incident on their side. We are currently working on it. .</p> <p><small>Nov <var data-var='date'> 15</var>, <var data-var='time'>14:08:41</var> GMT+0</small><br><strong>Resolved</strong> - The fix has been deployed and the incident has been resolved..</p> ]]> </content:encoded> <pubDate>Sat, 15 Nov 2025 13:00:13 +0000</pubDate> <link>https://wherebystatus.com/incident/cmi0ao4fi00i97aesjchppgr8</link> <guid>https://wherebystatus.com/incident/cmi0ao4fi00i97aesjchppgr8</guid> </item> <item> <title>Transcriptions might fail to save</title> <description> Type: Incident Duration: 1 hour and 35 minutes Affected Components: Meeting rooms Oct 24, 15:30:00 GMT+0 - Investigating - We are investigating the issue. Oct 24, 15:34:17 GMT+0 - Identified - We have identified the issue and we are working on a fix to solve the issue. Oct 24, 16:49:26 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 24, 17:05:23 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour and 35 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating the issue..</p> <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>15:34:17</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue and we are working on a fix to solve the issue..</p> <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>16:49:26</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>17:05:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Fri, 24 Oct 2025 15:30:00 +0000</pubDate> <link>https://wherebystatus.com/incident/cmh51rinj0216gyay2gblebxc</link> <guid>https://wherebystatus.com/incident/cmh51rinj0216gyay2gblebxc</guid> </item> <item> <title>Subscriptions errors at update + issues with new signups</title> <description> Type: Incident Duration: 1 day, 3 hours and 18 minutes Affected Components: whereby.com, Admin dashboard Oct 20, 10:33:00 GMT+0 - Resolved - AWS incident was resolved and everything in our service works as expected. Oct 20, 07:15:00 GMT+0 - Identified - One of our third party providers was affected by the AWS incident. There might be some issues with new signups and some subscriptions might not get properly updated. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 day, 3 hours and 18 minutes</p> <p><strong>Affected Components:</strong> , </p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>10:33:00</var> GMT+0</small><br><strong>Resolved</strong> - AWS incident was resolved and everything in our service works as expected..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>07:15:00</var> GMT+0</small><br><strong>Identified</strong> - One of our third party providers was affected by the AWS incident. There might be some issues with new signups and some subscriptions might not get properly updated. .</p> ]]> </content:encoded> <pubDate>Mon, 20 Oct 2025 07:15:00 +0000</pubDate> <link>https://wherebystatus.com/incident/cmh0b38gf0268q9ckllba8a2l</link> <guid>https://wherebystatus.com/incident/cmh0b38gf0268q9ckllba8a2l</guid> </item> <item> <title>Some rooms might experience issues due to an incident on a third-party provider</title> <description> Type: Incident Duration: 1 hour and 11 minutes Affected Components: Meeting rooms Aug 1, 15:36:28 GMT+0 - Investigating - Some rooms might experience issues due to an incident on a third-party provider. There may be longer connect times or disconnects. We are currently investigating this incident. Aug 1, 16:47:50 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 1 hour and 11 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>15:36:28</var> GMT+0</small><br><strong>Investigating</strong> - Some rooms might experience issues due to an incident on a third-party provider. There may be longer connect times or disconnects. We are currently investigating this incident. .</p> <p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>16:47:50</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Fri, 1 Aug 2025 15:36:28 +0000</pubDate> <link>https://wherebystatus.com/incident/cmdszkro602y314fb8q822o9q</link> <guid>https://wherebystatus.com/incident/cmdszkro602y314fb8q822o9q</guid> </item> <item> <title>Additional screen share fails to load</title> <description> Type: Incident Duration: 34 minutes Affected Components: Meeting rooms Jul 24, 08:30:46 GMT+0 - Investigating - We are currently investigating this incident. Jul 24, 08:55:42 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 24, 09:04:23 GMT+0 - Resolved - This incident has been resolved. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 34 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>08:30:46</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>08:55:42</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>09:04:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> </content:encoded> <pubDate>Thu, 24 Jul 2025 08:30:46 +0000</pubDate> <link>https://wherebystatus.com/incident/cmdh4ui94002nzjz7kcudggpb</link> <guid>https://wherebystatus.com/incident/cmdh4ui94002nzjz7kcudggpb</guid> </item> <item> <title>Whereby-hosted recordings / transcriptions unavailable</title> <description> Type: Incident Duration: 58 minutes Affected Components: Meeting rooms Feb 6, 10:02:29 GMT+0 - Resolved - The affected features are now working as normal Feb 6, 09:40:09 GMT+0 - Monitoring - Our storage provider has published a fix, which seems like it has solved the issue. We are currently monitoring Feb 6, 09:04:04 GMT+0 - Investigating - It seems like one of our storage providers is experiencing issues, preventing Whereby-hosted recordings and transcriptions from being stored. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 58 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>10:02:29</var> GMT+0</small><br><strong>Resolved</strong> - The affected features are now working as normal.</p> <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>09:40:09</var> GMT+0</small><br><strong>Monitoring</strong> - Our storage provider has published a fix, which seems like it has solved the issue. We are currently monitoring.</p> <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>09:04:04</var> GMT+0</small><br><strong>Investigating</strong> - It seems like one of our storage providers is experiencing issues, preventing Whereby-hosted recordings and transcriptions from being stored..</p> ]]> </content:encoded> <pubDate>Thu, 6 Feb 2025 09:04:04 +0000</pubDate> <link>https://wherebystatus.com/incident/cm6t427h6002vs7aiuu0bj4ut</link> <guid>https://wherebystatus.com/incident/cm6t427h6002vs7aiuu0bj4ut</guid> </item> <item> <title>No audio from iPhone users</title> <description> Type: Incident Affected Components: Meeting rooms Jan 14, 12:52:00 GMT+0 - Resolved - A recent change led to users on some iOS devices not transmitting audio to other participants in the room. The change has been rolled back and audio should now be working as expected. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>12:52:00</var> GMT+0</small><br><strong>Resolved</strong> - A recent change led to users on some iOS devices not transmitting audio to other participants in the room. The change has been rolled back and audio should now be working as expected..</p> ]]> </content:encoded> <pubDate>Tue, 14 Jan 2025 12:52:00 +0000</pubDate> <link>https://wherebystatus.com/incident/cm5wkmy350015kdokmf12ba76</link> <guid>https://wherebystatus.com/incident/cm5wkmy350015kdokmf12ba76</guid> </item> <item> <title>whereby.com down in ap-south region</title> <description> Type: Incident Duration: 22 hours and 8 minutes Affected Components: whereby.com Nov 27, 10:59:00 GMT+0 - Identified - We are receiving alerts that [whereby.com](http://whereby.com) is currently unavailable in the ap-south region (alerts are from Japan, South Korea, South Africa, India, Australia). Services remain unaffected (room, embedded and meeting dashboards). We are rolling back some recent configuration changes to restore availability in this region. Nov 28, 09:02:53 GMT+0 - Monitoring - We rolled back a recent update and are currently monitoring the result. The ap-south region is reporting that [whereby.com](http://whereby.com) is now available. Nov 28, 09:07:19 GMT+0 - Resolved - This incident has been resolved and access to [whereby.com](http://whereby.com) in ap-south region is fully restored. </description> <content:encoded> < is currently unavailable in the ap-south region (alerts are from Japan, South Korea, South Africa, India, Australia). Services remain unaffected (room, embedded and meeting dashboards). We are rolling back some recent configuration changes to restore availability in this region..</p> <p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>09:02:53</var> GMT+0</small><br><strong>Monitoring</strong> - We rolled back a recent update and are currently monitoring the result. The ap-south region is reporting that [whereby.com](http://whereby.com) is now available..</p> <p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>09:07:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved and access to [whereby.com](http://whereby.com) in ap-south region is fully restored..</p> ]]> </content:encoded> <pubDate>Wed, 27 Nov 2024 10:59:00 +0000</pubDate> <link>https://wherebystatus.com/incident/cm4133j34000g99jj5wi6f12c</link> <guid>https://wherebystatus.com/incident/cm4133j34000g99jj5wi6f12c</guid> </item> <item> <title>Website unavailable</title> <description> Type: Incident Duration: 14 minutes Affected Components: whereby.com Nov 27, 09:30:20 GMT+0 - Investigating - We are currently investigating this incident. Nov 27, 09:35:42 GMT+0 - Identified - Recent update has prevented access to our main site [whereby.com](http://whereby.com). We are in the process of initiating a rollback to restore the website. Services remain unaffected (room, embedded and meeting dashboards). Nov 27, 09:44:23 GMT+0 - Resolved - This incident has been resolved and access to [whereby.com](http://whereby.com) is restored. </description> <content:encoded> <. We are in the process of initiating a rollback to restore the website. Services remain unaffected (room, embedded and meeting dashboards)..</p> <p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>09:44:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved and access to [whereby.com](http://whereby.com) is restored..</p> ]]> </content:encoded> <pubDate>Wed, 27 Nov 2024 09:30:20 +0000</pubDate> <link>https://wherebystatus.com/incident/cm3zoqitm00052q92eoguirlp</link> <guid>https://wherebystatus.com/incident/cm3zoqitm00052q92eoguirlp</guid> </item> <item> <title>Upcoming Database Upgrade</title> <description> Type: Maintenance Duration: 30 minutes Affected Components: Embedded API, Admin dashboard, whereby.com, Meeting rooms Jul 15, 01:00:00 GMT+0 - Identified - Between 03:00 AM CEST and 03:30 AM CEST on July 15th, we'll be upgrading our databases. This will help us to boost the performance and reliability of our services. During this short window of time, our services may be temporarily unavailable. Unfortunately, there is no redundancy during this time, so if you can, we'd suggest that you do not schedule meetings during this period. We're sorry for any inconvenience this might cause. We always try to make these updates as seamless as possible, but sometimes a little downtime is unavoidable. Rest assured, we're already planning ways to reduce the impact of future upgrades. Jul 15, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 15, 01:30:00 GMT+0 - Completed - Maintenance has completed successfully </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Maintenance</p> <p><strong>Duration:</strong> 30 minutes</p> <p><strong>Affected Components:</strong> , , , </p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> - Between 03:00 AM CEST and 03:30 AM CEST on July 15th, we'll be upgrading our databases. This will help us to boost the performance and reliability of our services. During this short window of time, our services may be temporarily unavailable. Unfortunately, there is no redundancy during this time, so if you can, we'd suggest that you do not schedule meetings during this period. We're sorry for any inconvenience this might cause. We always try to make these updates as seamless as possible, but sometimes a little downtime is unavoidable. Rest assured, we're already planning ways to reduce the impact of future upgrades..</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>01:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>01:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> </content:encoded> <pubDate>Mon, 15 Jul 2024 01:00:00 +0000</pubDate> <link>https://wherebystatus.com/maintenance/clye3nti947494984oibj0oz749</link> <guid>https://wherebystatus.com/maintenance/clye3nti947494984oibj0oz749</guid> </item> <item> <title>Upcoming Database Upgrade</title> <description> Type: Maintenance Duration: 30 minutes Affected Components: Embedded API, Admin dashboard, whereby.com, Meeting rooms Jun 30, 01:30:00 GMT+0 - Completed - Maintenance has completed successfully Jun 30, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Jun 30, 01:00:00 GMT+0 - Identified - We will be performing necessary database maintenance to improve our infrastructure and enhance the performance and reliability of our services. During this maintenance, our services might be temporarily unavailable. There is no redundancy during this time. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Maintenance</p> <p><strong>Duration:</strong> 30 minutes</p> <p><strong>Affected Components:</strong> , , , </p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>01:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>01:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> - We will be performing necessary database maintenance to improve our infrastructure and enhance the performance and reliability of our services. During this maintenance, our services might be temporarily unavailable. There is no redundancy during this time..</p> ]]> </content:encoded> <pubDate>Sun, 30 Jun 2024 01:00:00 +0000</pubDate> <link>https://wherebystatus.com/maintenance/clxnd3fk246534bfoezeed9tgh</link> <guid>https://wherebystatus.com/maintenance/clxnd3fk246534bfoezeed9tgh</guid> </item> <item> <title>Whereby presentation website is down</title> <description> Type: Incident Duration: 11 minutes Affected Components: whereby.com Apr 22, 13:56:24 GMT+0 - Resolved - This incident has been resolved. Apr 22, 13:45:49 GMT+0 - Investigating - [whereby.com](http://whereby.com) is down. **This does not impact meeting rooms, API, or dashboard**. It only impacts the Whereby presentation website. We are currently investigating the issue. </description> <content:encoded> < is down. **This does not impact meeting rooms, API, or dashboard**. It only impacts the Whereby presentation website. We are currently investigating the issue..</p> ]]> </content:encoded> <pubDate>Mon, 22 Apr 2024 13:45:49 +0000</pubDate> <link>https://wherebystatus.com/incident/clvb0fjii72094b7oefr33w9mx</link> <guid>https://wherebystatus.com/incident/clvb0fjii72094b7oefr33w9mx</guid> </item> <item> <title>Cloud recordings stop unexpectedly</title> <description> Type: Incident Affected Components: Embedded API, Meeting rooms Feb 29, 10:35:55 GMT+0 - Resolved - We are noticing that cloud recordings end prematurely, roughly after 5 mins. We are deploying a potential fix. Feb 29, 11:47:21 GMT+0 - Resolved - An update to the underlying OS/runtime of our recording service caused recordings to crash after a few minutes. This crash was sadly not detected by our automated nor manual tests, which are always run before such deployments. The reason why we did not pick this up was the error only presented itself after a certain time, which is outside the time we have encoded in for our test runs. We have now rolled back the change and the feature should be working as expected. We are yet to find the root cause of the issue, and have scheduled time to identify what went wrong, and also discuss how our test setup can be adjusted to catch similar regressions in the future. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> , </p> <p><small>Feb <var data-var='date'> 29</var>, <var data-var='time'>10:35:55</var> GMT+0</small><br><strong>Resolved</strong> - We are noticing that cloud recordings end prematurely, roughly after 5 mins. We are deploying a potential fix..</p> <p><small>Feb <var data-var='date'> 29</var>, <var data-var='time'>11:47:21</var> GMT+0</small><br><strong>Resolved</strong> - An update to the underlying OS/runtime of our recording service caused recordings to crash after a few minutes. This crash was sadly not detected by our automated nor manual tests, which are always run before such deployments. The reason why we did not pick this up was the error only presented itself after a certain time, which is outside the time we have encoded in for our test runs. We have now rolled back the change and the feature should be working as expected. We are yet to find the root cause of the issue, and have scheduled time to identify what went wrong, and also discuss how our test setup can be adjusted to catch similar regressions in the future..</p> ]]> </content:encoded> <pubDate>Thu, 29 Feb 2024 10:35:55 +0000</pubDate> <link>https://wherebystatus.com/incident/clt73b5nx48699bjncsivptrzk</link> <guid>https://wherebystatus.com/incident/clt73b5nx48699bjncsivptrzk</guid> </item> <item> <title>Users might experience issues in large rooms (SFU rooms)</title> <description> Type: Incident Duration: 22 days and 6 hours Affected Components: Meeting rooms Feb 22, 17:29:00 GMT+0 - Resolved - This incident has been resolved. Feb 22, 08:35:00 GMT+0 - Identified - Due to some SFU crashes in Europe, users in this region might temporarily experience issues like black tiles or no audio from the other participants. We are currently working on a fix for the issue. Feb 22, 14:18:46 GMT+0 - Monitoring - We have implemented a fix and we are now monitoring it. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 22 days and 6 hours</p> <p><strong>Affected Components:</strong> </p> <p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>17:29:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>08:35:00</var> GMT+0</small><br><strong>Identified</strong> - Due to some SFU crashes in Europe, users in this region might temporarily experience issues like black tiles or no audio from the other participants. We are currently working on a fix for the issue..</p> <p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>14:18:46</var> GMT+0</small><br><strong>Monitoring</strong> - We have implemented a fix and we are now monitoring it. .</p> ]]> </content:encoded> <pubDate>Thu, 22 Feb 2024 08:35:00 +0000</pubDate> <link>https://wherebystatus.com/incident/clsx0ia8a22549c1mvyv1hcj6f</link> <guid>https://wherebystatus.com/incident/clsx0ia8a22549c1mvyv1hcj6f</guid> </item> <item> <title>Cloud recording might unexpectedly fail</title> <description> Type: Incident Duration: 4 hours and 6 minutes Affected Components: Meeting rooms Feb 20, 17:55:45 GMT+0 - Resolved - This incident has been resolved. Feb 20, 13:50:00 GMT+0 - Monitoring - Cloud recording might unexpectedly fail due to an on-going incident one of our providers is having. The issue has been identified, fixed and is currently monitored. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 4 hours and 6 minutes</p> <p><strong>Affected Components:</strong> </p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>17:55:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>13:50:00</var> GMT+0</small><br><strong>Monitoring</strong> - Cloud recording might unexpectedly fail due to an on-going incident one of our providers is having. The issue has been identified, fixed and is currently monitored. .</p> ]]> </content:encoded> <pubDate>Tue, 20 Feb 2024 13:50:00 +0000</pubDate> <link>https://wherebystatus.com/incident/clsuikfa9146891c2oew8kznco6</link> <guid>https://wherebystatus.com/incident/clsuikfa9146891c2oew8kznco6</guid> </item> <item> <title>Problems accessing rooms</title> <description> Type: Incident Affected Components: Meeting rooms Jan 26, 08:00:00 GMT+0 - Resolved - This morning we deployed some changes to our meeting experience which prevented some users accessing their rooms. After the first error report we rolled back our change and verified that users were able to access their rooms again. We have yet identified what exactly went wrong, as this only affected a subset of our users. Jan 26th 2024 ---------- 08:53 CET - Started deploy of new build which used script attribute crossorigin="anonymous" to allow us to get detailed insights into unhandled exceptions 08:59 CET - Deploy complete 09:18 CET - Got report from user not being able to access their room 09:21 CET - Started rollback to latest working version 09:29 CET - Rollback complete, verified the failing changes had been removed So downtime (for some users) was roughly between 09:00 CET and 09:30 CET </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This morning we deployed some changes to our meeting experience which prevented some users accessing their rooms. After the first error report we rolled back our change and verified that users were able to access their rooms again. We have yet identified what exactly went wrong, as this only affected a subset of our users. Jan 26th 2024 ---------- 08:53 CET - Started deploy of new build which used script attribute crossorigin="anonymous" to allow us to get detailed insights into unhandled exceptions 08:59 CET - Deploy complete 09:18 CET - Got report from user not being able to access their room 09:21 CET - Started rollback to latest working version 09:29 CET - Rollback complete, verified the failing changes had been removed So downtime (for some users) was roughly between 09:00 CET and 09:30 CET .</p> ]]> </content:encoded> <pubDate>Fri, 26 Jan 2024 08:00:00 +0000</pubDate> <link>https://wherebystatus.com/incident/clruhpe0j25293bmlmtjvtnyo7</link> <guid>https://wherebystatus.com/incident/clruhpe0j25293bmlmtjvtnyo7</guid> </item> <item> <title>Business trial signup issues</title> <description> Type: Incident Affected Components: whereby.com Sep 6, 17:15:32 GMT+0 - Resolved - We've reverted some changes in our signup flow that were causing unexpected issues during the business signup flow. The trial signup process is now working as expected </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Affected Components:</strong> </p> <p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>17:15:32</var> GMT+0</small><br><strong>Resolved</strong> - We've reverted some changes in our signup flow that were causing unexpected issues during the business signup flow. The trial signup process is now working as expected.</p> ]]> </content:encoded> <pubDate>Wed, 6 Sep 2023 17:15:32 +0000</pubDate> <link>https://wherebystatus.com/incident/clm80349y324727bvonw4aarjii</link> <guid>https://wherebystatus.com/incident/clm80349y324727bvonw4aarjii</guid> </item> <item> <title>Bug in insight data collection</title> <description> Type: Incident Duration: 11 days and 21 hours Affected Components: Admin dashboard Aug 29, 08:15:00 GMT+0 - Investigating - Room Insights participant logs are impacted for all users that used screensharing in their sessions Sep 4, 15:00:00 GMT+0 - Resolved - This issue has now been resolved, but the data during this period involving participant detail logs may be incomplete. Billing, calculation of participant minutes and room level and room session level insights remained unaffected throughout this period. This issue only affected detailed participant data in the administration dashboard. </description> <content:encoded> <![CDATA[<p><strong>Type:</strong> Incident</p> <p><strong>Duration:</strong> 11 days and 21 hours</p> <p><strong>Affected Components:</strong> </p> <p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>08:15:00</var> GMT+0</small><br><strong>Investigating</strong> - Room Insights participant logs are impacted for all users that used screensharing in their sessions .</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This issue has now been resolved, but the data during this period involving participant detail logs may be incomplete. Billing, calculation of participant minutes and room level and room session level insights remained unaffected throughout this period. This issue only affected detailed participant data in the administration dashboard..</p> ]]> </content:encoded> <pubDate>Tue, 29 Aug 2023 08:15:00 +0000</pubDate> <link>https://wherebystatus.com/incident/clm52sxhp9298arn94dph62cp</link> <guid>https://wherebystatus.com/incident/clm52sxhp9298arn94dph62cp</guid> </item> </channel> </rss>