Incidents reported on status page for TeamBridge https://teambridge.betteruptime.com/ https://d1lppblt9t2x15.cloudfront.net/logos/d61c22d0c911d32ae7f24f13da5bd5d3.png https://teambridge.betteruptime.com/ en https://teambridge.betteruptime.com/ Thu, 26 Jun 2025 00:38:31 +0000 https://teambridge.betteruptime.com/#61056abfddb419e5704333390ad08d786f9bee881f244a19561c3581098b6e82 Platform Backend recovered https://teambridge.betteruptime.com/ Thu, 26 Jun 2025 00:35:38 +0000 https://teambridge.betteruptime.com/#61056abfddb419e5704333390ad08d786f9bee881f244a19561c3581098b6e82 Platform Backend went down https://teambridge.betteruptime.com/incident/392095 Mon, 01 Jul 2024 19:20:00 -0000 https://teambridge.betteruptime.com/incident/392095#cc626d029c0c6e39b46537f1c0f12d2fe4cc7281936f00571e630ea6e22a6f19 At 10:10am PST on July 1st we saw two spikes in CPU for mobile dashboard queries that we believe overloaded the database. Once the CPU load went down, we were able to get the server back online. Our engineering team pushed out a fix to the problematic queries as well as a backup reader in case the system is overloaded again. https://teambridge.betteruptime.com/incident/392095 Mon, 01 Jul 2024 19:20:00 -0000 https://teambridge.betteruptime.com/incident/392095#cc626d029c0c6e39b46537f1c0f12d2fe4cc7281936f00571e630ea6e22a6f19 At 10:10am PST on July 1st we saw two spikes in CPU for mobile dashboard queries that we believe overloaded the database. Once the CPU load went down, we were able to get the server back online. Our engineering team pushed out a fix to the problematic queries as well as a backup reader in case the system is overloaded again. https://teambridge.betteruptime.com/incident/377126 Fri, 24 May 2024 21:20:00 -0000 https://teambridge.betteruptime.com/incident/377126#9c1b373832b2fa75b8f60d9be03d6c0079dbf0977d92b4016fd72adc5309c432 At 11:20am PST on May 24th we were alerted that our backend was down. Upon investigation, we found that our database connections were failing due to an inefficient looped query that was causing locks in our database. We identified the problem in our code and cleared all the locks to get the server back online. Our engineering team pushed out a fix to prevent this query from locking the database again. https://teambridge.betteruptime.com/incident/377126 Fri, 24 May 2024 21:20:00 -0000 https://teambridge.betteruptime.com/incident/377126#9c1b373832b2fa75b8f60d9be03d6c0079dbf0977d92b4016fd72adc5309c432 At 11:20am PST on May 24th we were alerted that our backend was down. Upon investigation, we found that our database connections were failing due to an inefficient looped query that was causing locks in our database. We identified the problem in our code and cleared all the locks to get the server back online. Our engineering team pushed out a fix to prevent this query from locking the database again. https://teambridge.betteruptime.com/incident/333800 Mon, 11 Mar 2024 08:00:00 +0000 https://teambridge.betteruptime.com/incident/333800#80c8c879ed3e155784eb3d816efd94d49fea1ce722cf9039bb14ca686791b459 Maintenance completed https://teambridge.betteruptime.com/incident/333800 Mon, 11 Mar 2024 07:00:00 -0000 https://teambridge.betteruptime.com/incident/333800#3e165906b43e5776ebaceb2f083ce6a3a7eac994a765db8b5eb8618b9e3af07d Web dashboard may experience temporary interruptions while we launch maintenance updates and bug fixes.