Whereby had 18 outages in the last 2 years totaling 147h 50m of downtime — averaging 0.7 incidents per month.
There were 18 Whereby outages since November 27, 2024 totaling 147h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating failed and slow responses from our customer insights api
We have cleared out some long-running jobs affecting the performance, monitoring....
This incident has been resolved.
We are currently investigating this incident..
This incident has been resolved..
We are currently investigating this incident..
This incident has been resolved..
We are continuing to work on a fix for this incident.
This incident has been resolved.
We are currently investigating an incident affecting streaming for all users. Streaming is unavailable at this time.
This incident has been resolved.
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..
**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..
We are continuing to work on a fix for this incident together with the third party provider..
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..
We are continuing to work on a fix for this incident..
This incident has been resolved..
We are investigating the issue..
We have identified the issue and we are continuing to work on a fix for this incident..
This incident has been resolved..
We are currently investigating this incident..
.
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..
This incident has been resolved..
We implemented a fix and are currently monitoring the result..
.
Our third party provider has an incident. We are currently investigating the incident..
We have identified an alternative solution until our provider solves the incident on their side. We are currently working on it. .
The fix has been deployed and the incident has been resolved..
We are investigating the issue..
We have identified the issue and we are working on a fix to solve the issue..
We implemented a fix and are currently monitoring the result..
This incident has been resolved..
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. .
AWS incident was resolved and everything in our service works as expected..
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. .
This incident has been resolved..
We are currently investigating this incident..
We implemented a fix and are currently monitoring the result..
This incident has been resolved..
It seems like one of our storage providers is experiencing issues, preventing Whereby-hosted recordings and transcriptions from being stored..
Our storage provider has published a fix, which seems like it has solved the issue. We are currently monitoring.
The affected features are now working as normal.
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..
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..
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..
This incident has been resolved and access to [whereby.com](http://whereby.com) in ap-south region is fully restored..
We are currently investigating this incident..
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)..
This incident has been resolved and access to [whereby.com](http://whereby.com) is restored..