Callbridge Outage History

Started May 28, 2026, 08:19 PM UTC· resolved May 29, 2026, 03:45 AM UTC

1. identified May 28, 2026, 08:19 PM UTC

   The issue has been identified, and the solution is under work.

2. resolved May 29, 2026, 02:03 PM UTC

   This incident has been resolved.

3. postmortem May 29, 2026, 03:01 PM UTC

   Between May 28, 2026, at 15:30 UTC and May 29, 2026, at 03:30 UTC, our platform experienced an email delivery outage. During this 12-hour period, system-generated emails were not successfully delivered.

Read the full incident report →

Started Feb 27, 2026, 03:12 PM UTC· resolved Feb 27, 2026, 04:17 PM UTC

1. identified Feb 27, 2026, 03:12 PM UTC

   We are currently experiencing intermittent disruption to our web conferencing services. Our team is diligently working to resolve this issue. We will follow up with an email as soon as the service has been restored.

2. resolved Feb 27, 2026, 04:17 PM UTC

   This incident has been resolved as of 02/27/2026 15:50 UTC

Read the full incident report →

Started Jul 14, 2025, 04:25 PM UTC· resolved Jul 31, 2025, 07:38 PM UTC

1. investigating Jul 14, 2025, 04:25 PM UTC

   We've identified a new issue where Chrome and Edge tabs may close unexpectedly during video meetings on our platform. We've already submitted a bug report to the Chromium team and are actively collaborating with them to investigate and resolve this as quickly as possible. In the meantime, downloading and installing our app will resolve this issue for you. https://support.callbridge.com/support/solutions/articles/42000113823-chrome-138-update

2. monitoring Jul 28, 2025, 08:16 PM UTC

   Chrome 138 – Update on Video Freezing and Crashing Issues Two separate issues have occurred in recent weeks: video freezing/spinning, and browser crashes. After extensive analysis, both have been traced back to changes introduced in Chrome 138. 1. Video freezing or spinning: Chrome 138 was the cause of this issue. We’ve deployed updates to our video servers to resolve it. We’re confident this issue is fully addressed. 2. Browser crashing: This issue is also linked to Chrome 138. We have traced this Chrome bug to their AV1 video codec implementation, and have a working thesis that this is correct. We have disabled the AV1 codec in production, reverting to VP9. In our internal testing, this prevents Chrome from crashing. We continue monitoring this to confirm its effectiveness across all environments. 3. It’s unclear whether these issues were present in early versions of Chrome or were introduced after the stable release. Although we already test beta releases of Chrome, we are expanding our QA process to include longer, more detailed testing across a broader range of devices and browser versions to help us catch similar issues earlier in the future.

3. resolved Jul 31, 2025, 07:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 22, 2024, 07:19 PM UTC· resolved Nov 22, 2024, 10:04 PM UTC

1. identified Nov 22, 2024, 07:19 PM UTC

   We are currently experiencing intermittent delayed service response with the conferencing services. Our team is diligently working to resolve this issue. We will follow up with an email once the service has been restored.

2. monitoring Nov 22, 2024, 07:36 PM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Nov 22, 2024, 07:49 PM UTC

   We are continuing to monitor for any further issues.

4. identified Nov 22, 2024, 09:17 PM UTC

   We continue to investigate the delayed response to the service. We will update the Status page as soon as a resolution is in place.

5. resolved Nov 22, 2024, 10:04 PM UTC

   We identified an issue caused by the Google Calendar add-on, which impacted the performance of our video conferencing platform. To resolve this issue, we have temporarily disabled some Google Calendar integration features. The core video conferencing platform is now fully functional, and we are working to restore the add-on features as quickly as possible. We sincerely apologize for any inconvenience caused and appreciate your understanding as we address this matter.

6. postmortem Nov 26, 2024, 08:31 PM UTC

   ## Summary of Root Cause Google Workspace made some internal changes at around the beginning of November 2024, which changes the Google Calendar add-on behavior. We have observed that the add-on would resubmit the same meeting changes to our platform during event synchronization and caused a large increase in the number of API requests. Google’s platform also has a “request quota“ which was then triggered and resulted in blocking the requests to our platform. This in turn would queue up more requests for the next event batch to synchronize the changes. After a couple of weeks of random interruptions to the Google Calendar add-on, it reached a point where the concurrent requests to change existing meeting schedules are causing database deadlock and transaction rollbacks. The database was bogged down doing transaction rollbacks during the incident window causing the meeting scheduling and starting/joining meetings to time out, for some or even most users. ## Action Plan to Prevent Future Service Incidents * We have disabled all Google Calendar add-ons on 11/25 * We will rewrite how we process the Google Calendar updates so that all changes to a given account are serialized \(instead of updating meetings in parallel\) * We will collect logs to open a ticket with Google Workspace team to understand their changes ## Timeline \(UTC\) * 11/5 - 11/15: internal system alert showing increased amount of requests from Google Calendar add-on \(partner 1\) and elevated system stress. The affected meeting linked to most of the requests was flagged to be bypassed for future request processing. Several reports about issues using Google Calendar add-on \(multiple partners\). We have rolled out several changes to reduce the performance impact on the system resources caused by the large amount of requests. We also reached a conclusion that Google Workspace was blocking/throttling requests to us. * 11/13 17:40 - 18:35: the database experienced a deadlock, causing several components to timeout. We scaled up the system to increase capacity, meanwhile Google Workspace paused the requests to us. The combination resolved the service incident. * 11/22 19:10 - 22:00: the database experienced a deadlock, causing several components to timeout. We flushed all the system nodes to clear the deadlock, but it did not resolve the issue. We then identified and blocked 2 Google Calendar add-on that are sending the most requests and resolved the service incident. * 11/25 16:30 - 16:40: the database experienced a deadlock, causing the platform to be very slow. We decided to disable all Google Calendar add-on. ## Method of Discovery Customers started reporting unusual service behavior with their meetings. ## Scope of Impact Service was slow to react when trying to get to the meeting dashboard, starting a meeting, giving errors when scheduling a call. All in meeting features such as recording, chat and muting were unresponsive or very slow to respond. Some users were disconnected from their meetings. ## Resolution The Google Calendar Add-on was disabled stopping all API requests to synchronize events

Read the full incident report →

Started Nov 13, 2024, 05:45 PM UTC· resolved Nov 13, 2024, 06:37 PM UTC

1. identified Nov 13, 2024, 05:45 PM UTC

   The web conferencing service is currently experiencing a higher than normal amount of load, and may be causing pages to be slow or unresponsive. We're investigating the cause and will provide an update as soon as possible. Note that your telephone conferencing services have NOT been impacted in any way.

2. resolved Nov 13, 2024, 06:37 PM UTC

   Service is now fully restored as of 11/13/2024 6:36 p.m. UTC (11:36 Eastern).

Read the full incident report →